Triple
T35724885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Red Line |
E1032581
|
entity |
| Predicate | hasLineCodeType |
P56964
|
FINISHED |
| Object | color-coded line |
—
|
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: color-coded line | Statement: [Dark Red Line, hasLineCodeType, color-coded line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLineCodeType Context triple: [Dark Red Line, hasLineCodeType, color-coded line]
-
A.
usesLineCode
Indicates that one entity employs or references a specific line code as part of its operation, identification, or communication.
-
B.
hasTypeCode
chosen
Indicates that an entity is associated with a specific type classification represented by a code.
-
C.
hasLine3Code
Indicates that an entity is associated with a specific third-line code, typically representing a tertiary or additional coding value in a multi-line or hierarchical code system.
-
D.
hasJrLineCode
Indicates that an entity is associated with a specific junior (JR) line code identifier within a system or classification.
-
E.
hasLineCharacter
Indicates that one entity possesses or includes a specific character or symbol that appears within a line of text or sequence.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69febce5877c8190a5e000ef5331ec88 |
completed | May 9, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69febad1cd588190abc7686bcb39a371 |
completed | May 9, 2026, 4:40 a.m. |
Created at: May 3, 2026, 4:05 p.m.