Triple
T7915237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christopher Courtney |
E183806
|
entity |
| Predicate | serviceDuringPeriod |
P15403
|
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: [Christopher Courtney, serviceDuringPeriod, early years of the Second World War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceDuringPeriod Context triple: [Christopher Courtney, serviceDuringPeriod, early years of the Second World War]
-
A.
serviceDuring
chosen
Indicates that one entity performs or provides a service for another entity during a specified time period or event.
-
B.
serviceEntryPeriod
Indicates the span of time during which a service is active, valid, or in effect for the related entities.
-
C.
serviceOpenedBetween
Indicates that a service has been initiated or made available during the time interval between two specified points or events.
-
D.
serviceDays
Indicates the specific days on which a service is provided or operates.
-
E.
sawServicePeriod
Indicates that one entity observed or was aware of the duration or specific period during which a service was provided or active.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a759b548190af2e2aa0705d7051 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:05 p.m.