Triple
T14832504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spirit of St. Louis |
E348741
|
entity |
| Predicate | yearOfServiceEntry |
P93707
|
FINISHED |
| Object | 1927 |
—
|
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: 1927 | Statement: [Spirit of St. Louis, yearOfServiceEntry, 1927]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfServiceEntry Context triple: [Spirit of St. Louis, yearOfServiceEntry, 1927]
-
A.
serviceNumberOrYearsOfService
Indicates a relationship that specifies either an entity’s service identification number or the duration of time the entity has served.
-
B.
yearsOfMilitaryService
Indicates the number of years an entity has served or is recorded as serving in the military.
-
C.
hasTimePeriodOfService
Indicates that an entity is associated with a specific span of time during which it provided service or was actively serving.
-
D.
militaryServicePeriod
Indicates the span of time during which an entity serves or has served in a military capacity.
-
E.
enlistmentYear
chosen
Indicates the year in which an entity formally joined or was enrolled into a service, organization, or group.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded075af0881908fb35a9e7ee46749 |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:52 a.m.