Triple
T27696940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Pacific AC-8 |
E698321
|
entity |
| Predicate | operatedUntilApprox |
P6603
|
FINISHED |
| Object | late 1950s |
—
|
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: late 1950s | Statement: [Southern Pacific AC-8, operatedUntilApprox, late 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedUntilApprox Context triple: [Southern Pacific AC-8, operatedUntilApprox, late 1950s]
-
A.
operatedUntil
chosen
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
B.
operatedAt
Indicates that an operation, procedure, or activity was performed at a specific location or facility.
-
C.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
-
D.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
E.
intendedToServeUntil
Indicates that an entity was planned or expected to remain in a particular role, function, or state up to a specified end time or condition.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: April 27, 2026, 2:54 p.m.