Triple
T8684671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birchanger Green services |
E206126
|
entity |
| Predicate | hasSignageOn |
P5950
|
FINISHED |
| Object | M11 motorway |
—
|
NE NERFINISHED |
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: M11 motorway | Statement: [Birchanger Green services, hasSignageOn, M11 motorway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignageOn Context triple: [Birchanger Green services, hasSignageOn, M11 motorway]
-
A.
hasSignageIn
Indicates that appropriate signs or signage for an entity are present or installed within a specified location or area.
-
B.
hasSignage
chosen
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
C.
hasSignageType
Indicates the specific category or kind of signage associated with an object, location, or entity.
-
D.
hasSignageName
Indicates that an entity has a specific name or label as it appears on its physical signage.
-
E.
hasSignagePrefix
Indicates that one signage element begins with or contains another signage element as its initial segment or prefix.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4aeae740819099093906ccc5f640 |
completed | March 31, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.