Triple
T28525487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piedmont and Northern Railway |
E721892
|
entity |
| Predicate | hadSeparateDivision |
P126426
|
FINISHED |
| Object | North Carolina Division |
—
|
NE NERFINISHED |
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: North Carolina Division | Statement: [Piedmont and Northern Railway, hadSeparateDivision, North Carolina Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSeparateDivision Context triple: [Piedmont and Northern Railway, hadSeparateDivision, North Carolina Division]
-
A.
wasDividedBetween
Indicates that something was partitioned into portions that were allocated to two or more distinct recipients or groups.
-
B.
hadInternalDivision
Indicates that an entity experienced a split or conflict within its own members, factions, or components.
-
C.
hadSeparateBranch
chosen
Indicates that one entity maintained a distinct, independent branch or subdivision separate from another entity.
-
D.
hadDivisionInCountry
Indicates that an organization or entity maintained a formal division, branch, or subsidiary operating within a specified country.
-
E.
wasDividedFrom
Indicates that one entity was separated or split off from another entity, resulting in two distinct parts or groups.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fa5ea0c819086708d4430a90a54 |
completed | May 2, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:24 a.m.