Triple
T20921295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N scale |
E515213
|
entity |
| Predicate | typicalTrackCode |
P141685
|
FINISHED |
| Object | Code 80 |
—
|
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: Code 80 | Statement: [N scale, typicalTrackCode, Code 80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTrackCode Context triple: [N scale, typicalTrackCode, Code 80]
-
A.
trackType
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
B.
trailNumber
Indicates that an entity is associated with a specific trail identifier or route number within a trail system.
-
C.
trackingType
Indicates the method or category by which an entity’s movement, status, or progress is monitored or recorded.
-
D.
typicalSegmentType
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
-
E.
trackPattern
Indicates that one entity follows, monitors, or records the behavior or state of another according to a defined pattern or sequence.
- 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_69e0b4f9d5ec8190bb2bd27350ed341c |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f64e56bc81908aa86f2176fcc0db |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:48 p.m.