Triple
T20172938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1996 Stock |
E492012
|
entity |
| Predicate | originalFormation |
P36931
|
FINISHED |
| Object | 6-car train |
—
|
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: 6-car train | Statement: [1996 Stock, originalFormation, 6-car train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalFormation Context triple: [1996 Stock, originalFormation, 6-car train]
-
A.
primaryFormation
chosen
Indicates that one entity serves as the main or original formation or structural configuration associated with another entity.
-
B.
originalForm
Indicates that one entity is the earlier, source, or initial version from which another entity is derived or transformed.
-
C.
onFormation
Indicates that one entity is located on or attached to the surface of a formation (such as a geological or structural feature).
-
D.
associatedFormation
Indicates that one entity is linked or connected to a particular formation, such as a geological, structural, or organizational configuration.
-
E.
originalFormulation
Indicates that one entity is the initial or earliest version in which another entity (such as an idea, work, or product) was first expressed or formulated.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66849709c81909b65b421282f9f3b |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.