Triple
T1782740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brill streetcar |
E39323
|
entity |
| Predicate | typicalTrackType |
P3832
|
FINISHED |
| Object | grooved rail in paved streets |
—
|
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: grooved rail in paved streets | Statement: [Brill streetcar, typicalTrackType, grooved rail in paved streets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTrackType Context triple: [Brill streetcar, typicalTrackType, grooved rail in paved streets]
-
A.
trackType
chosen
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
B.
typicalSegmentType
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
-
C.
trajectoryType
Indicates the kind or pattern of motion an entity follows along its path over time.
-
D.
trackingType
Indicates the method or category by which an entity’s movement, status, or progress is monitored or recorded.
-
E.
typicalCoreType
Indicates that something is a standard or characteristic core type within a given classification or 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.