Triple
T9472554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Crew Europe Star |
E228426
|
entity |
| Predicate | periodOfService |
P75989
|
FINISHED |
| Object | early years of the Second World War |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: early years of the Second World War | Statement: [Air Crew Europe Star, periodOfService, early years of the Second World War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfService Context triple: [Air Crew Europe Star, periodOfService, early years of the Second World War]
-
A.
militaryServicePeriod
Indicates the span of time during which an entity serves or has served in a military capacity.
-
B.
hasTimePeriodOfService
chosen
Indicates that an entity is associated with a specific span of time during which it provided service or was actively serving.
-
C.
yearsOfMilitaryService
Indicates the number of years an entity has served or is recorded as serving in the military.
-
D.
yearsMissedForMilitaryService
Indicates the number of years an entity did not participate in an activity or role due to serving in the military.
-
E.
periodOfRAFService
Indicates the time span during which an entity served in the Royal Air Force (RAF).
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7ff0afd08190871b68a88fdbff2b |
completed | April 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:54 p.m.