Triple
T20088730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nickel Plate Road 2-8-4 Berkshires |
E496208
|
entity |
| Predicate | whyBerkshireName |
P7885
|
FINISHED |
| Object | named for the Berkshire Mountains where the type was first tested |
—
|
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: named for the Berkshire Mountains where the type was first tested | Statement: [Nickel Plate Road 2-8-4 Berkshires, whyBerkshireName, named for the Berkshire Mountains where the type was first tested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: whyBerkshireName Context triple: [Nickel Plate Road 2-8-4 Berkshires, whyBerkshireName, named for the Berkshire Mountains where the type was first tested]
-
A.
reasonForName
chosen
Indicates the explanation or cause behind why an entity has a particular name.
-
B.
districtNameOrigin
Indicates that the relationship specifies the origin or source from which a district’s name is derived.
-
C.
reasonForEpithet
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
D.
hasPlaceNamedAfter
Indicates that one place is named in honor of or derived from the name of another place.
-
E.
labelFounded
Indicates that one entity established or created another entity, typically marking the origin or founding event.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6655d65a88190a510132f36341b6c |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:17 p.m.