Triple
T5786748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red route network |
E128285
|
entity |
| Predicate | singleRedLineMeaning |
P4987
|
FINISHED |
| Object | no stopping at times shown on nearby signs |
—
|
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: no stopping at times shown on nearby signs | Statement: [Red route network, singleRedLineMeaning, no stopping at times shown on nearby signs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singleRedLineMeaning Context triple: [Red route network, singleRedLineMeaning, no stopping at times shown on nearby signs]
-
A.
whiteStripeMeaning
Indicates that one entity has a white stripe pattern or marking that is significant or characteristic in the context of the relationship.
-
B.
mapColor_RedLine
Indicates that a map element is represented or highlighted using a red line.
-
C.
greenStripeMeaning
Indicates that something has a stripe colored green or marked with green striping.
-
D.
redStripeMeaning
chosen
Indicates that something has a red-colored stripe and conveys the meaning, symbolism, or significance associated with that red stripe.
-
E.
lineSymbol
Indicates that one entity is used as a line-style or line-representation symbol for another entity.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a1c29d48190af36cc855bb491dd |
completed | March 22, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.