Triple
T2841896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alf Landon |
E62487
|
entity |
| Predicate | served as |
P1827
|
FINISHED |
| Object | private in World War I (non-combat stateside service) |
—
|
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: private in World War I (non-combat stateside service) | Statement: [Alf Landon, served as, private in World War I (non-combat stateside service)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: served as Context triple: [Alf Landon, served as, private in World War I (non-combat stateside service)]
-
A.
servedAs
chosen
Indicates that one entity held and performed the role, position, or function associated with another entity for some period of time.
-
B.
served
Indicates that one entity provided a service, assistance, or role-based function to or for another entity.
-
C.
servedInRole
Indicates that one entity performed duties or held a position within a specified role or office in relation to another entity.
-
D.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
E.
servedWith
Indicates that one item is customarily presented, provided, or consumed together with another as an accompaniment or side.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf16d0c08190bb8de4a4160b4414 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.