Triple
T34355263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francis Street |
E881701
|
entity |
| Predicate | roadRulesFollow |
P7767
|
FINISHED |
| Object | left-hand traffic |
—
|
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: left-hand traffic | Statement: [Francis Street, roadRulesFollow, left-hand traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadRulesFollow Context triple: [Francis Street, roadRulesFollow, left-hand traffic]
-
A.
roadTrafficRuleJurisdiction
chosen
Indicates the jurisdiction or authority under whose road traffic rules a given situation, entity, or action is governed.
-
B.
hasRoadSign
Indicates that one entity possesses, displays, or is associated with a particular road sign.
-
C.
נוהגים_ב
Indicates a manner or customary way in which someone treats, behaves toward, or deals with someone or something.
-
D.
hasRoadSignConvention
Indicates that there is an established standard or system governing the design, meaning, or usage of road signs in a given context.
-
E.
roadSignageIndicates
Indicates that a piece of road signage conveys, displays, or communicates specific information, instructions, or warnings about road conditions or regulations.
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:58 a.m.