Triple
T10589693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Loop |
E249949
|
entity |
| Predicate | signposted |
P66816
|
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: [London Loop, signposted, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signposted Context triple: [London Loop, signposted, yes]
-
A.
signpostFeature
Indicates that one entity serves as a signpost-related feature or element associated with another entity.
-
B.
roadSignageIndicates
Indicates that a piece of road signage conveys, displays, or communicates specific information, instructions, or warnings about road conditions or regulations.
-
C.
roadSignPrefix
Indicates a relationship where one element serves as the initial or leading part of a road sign’s text, code, or designation.
-
D.
hasRoadSign
chosen
Indicates that one entity possesses, displays, or is associated with a particular road sign.
-
E.
usedOnRoadSigns
Indicates that something (such as a symbol, color, or material) is employed in the design or construction of road signs.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5277a39f08190848f24752cfa4b8f |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:40 p.m.