Triple
T12479283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S8 Stock |
E298260
|
entity |
| Predicate | hasCabAtEachEnd |
P105222
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [S8 Stock, hasCabAtEachEnd, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCabAtEachEnd Context triple: [S8 Stock, hasCabAtEachEnd, yes]
-
A.
hasCabPosition
Indicates that an entity has a specific position or placement of a cab relative to its overall structure or configuration.
-
B.
hasCabType
Indicates that an entity is associated with or characterized by a specific type or category of cab.
-
C.
hasDoublePoleAt
Indicates that a function or expression has a pole of order two (a second-order singularity) at a specified point.
-
D.
hasCapitalOnOneSide
Indicates that one entity has its capital city located on one side (e.g., bank, shore, border) of the other entity.
-
E.
locatedAtTerminusOf
Indicates that one entity is situated at the end point or final terminus of another entity, such as a route, line, or path.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d94e5f8d04819086d1ad4d62364005 |
completed | April 10, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:56 p.m.