Triple
T3552413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LIRR Hempstead Branch |
E75139
|
entity |
| Predicate | usesControlSystem |
P43307
|
FINISHED |
| Object | centralized traffic control |
—
|
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: centralized traffic control | Statement: [LIRR Hempstead Branch, usesControlSystem, centralized traffic control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesControlSystem Context triple: [LIRR Hempstead Branch, usesControlSystem, centralized traffic control]
-
A.
usedCommandAndControlSystem
Indicates that an entity employed a specific command-and-control system to coordinate, manage, or direct operations or activities.
-
B.
canControl
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
C.
controlMethods
chosen
Indicates the methods or techniques used by one entity to direct, regulate, or influence the behavior, operation, or state of another entity.
-
D.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
E.
robotControlSystem
Indicates a relationship where a system monitors, directs, and coordinates the actions and behaviors of one or more robots.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc05256f081908b8d6a5df917e679 |
completed | March 8, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:20 p.m.