Triple
T20393990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STM |
E500151
|
entity |
| Predicate | networkCodeType |
P2202
|
FINISHED |
| Object | LIRR internal station code |
—
|
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: LIRR internal station code | Statement: [STM, networkCodeType, LIRR internal station code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkCodeType Context triple: [STM, networkCodeType, LIRR internal station code]
-
A.
networkCode
Indicates that an entity is associated with, identified by, or operates under a specific network code within a communication or organizational network.
-
B.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
C.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
D.
telecommunicationsType
Indicates the specific category or mode of telecommunications service or technology associated with an entity.
-
E.
codeType
chosen
Indicates the classification or category assigned to a particular code within a coding or encoding system.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e679122058819083e3615a5ea0a82e |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:28 a.m.