Triple
T35231183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesee & Wyoming Inc. |
E1017237
|
entity |
| Predicate | hasMajorOperation |
P37052
|
FINISHED |
| Object | United States |
E14
|
NE 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: United States | Statement: [Genesee & Wyoming Inc., hasMajorOperation, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorOperation Context triple: [Genesee & Wyoming Inc., hasMajorOperation, United States]
-
A.
hasMajorOperator
Indicates that an entity is primarily operated, managed, or run by a specified main operator or organization.
-
B.
hasMainOperations
Indicates that an entity is associated with its primary or core operations, activities, or functions.
-
C.
hasNotableOperation
Indicates that an entity is associated with a significant or noteworthy operation, activity, or procedure.
-
D.
hasMajorWork
Indicates that an entity (typically a person, creator, or organization) is associated with a significant or principal work they produced or are best known for.
-
E.
hasGlobalOperationsIn
chosen
Indicates that an entity conducts business or operational activities across multiple countries within the specified region or location.
- F. None of above.
Provenance (4 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a020ec13d808190b41acdc31adc4191 |
completed | May 11, 2026, 5:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3823afe13c81908e38e410793e382d |
completed | June 21, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_6a020d9259c08190ad0370091c23ea8a |
completed | May 11, 2026, 5:10 p.m. |
Created at: May 3, 2026, 4:02 p.m.