Triple
T553025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5 train |
E11881
|
entity |
| Predicate | compatibleWithSignaling |
P16280
|
FINISHED |
| Object | IRT signaling standards |
—
|
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: IRT signaling standards | Statement: [5 train, compatibleWithSignaling, IRT signaling standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compatibleWithSignaling Context triple: [5 train, compatibleWithSignaling, IRT signaling standards]
-
A.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
B.
coSignedWith
Indicates that an entity has jointly signed a document, agreement, or obligation together with another entity.
-
C.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
D.
backwardCompatibleWith
Indicates that one entity can correctly interpret, use, or function with data, interfaces, or behavior designed for an earlier version of another entity.
-
E.
signedTogetherWith
Indicates that one entity signed a document, agreement, or contract jointly with another entity.
- F. None of above. chosen
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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4991b296481908cf27e1d1ec67052 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494bc1f8c8190904356f3a8e801de |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985952a481908b918350ececf484 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.