Triple
T8017852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Märklin |
E186664
|
entity |
| Predicate | trackSystem |
P80589
|
FINISHED |
| Object | three-rail AC system |
—
|
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: three-rail AC system | Statement: [Märklin, trackSystem, three-rail AC system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackSystem Context triple: [Märklin, trackSystem, three-rail AC system]
-
A.
rackSystem
Indicates a relationship where an entity functions as or belongs to a particular rack-based storage or mounting system.
-
B.
track
Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
-
C.
trackOn
Indicates that one entity is physically positioned or moving along the surface or path of another, like a vehicle on a track or rails.
-
D.
trackingAvailable
Indicates that tracking information or functionality is available for the associated item, process, or interaction.
-
E.
trackingType
Indicates the method or category by which an entity’s movement, status, or progress is monitored or recorded.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df4f1b8819089a8b67f136bce9a |
completed | March 31, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:20 p.m.