Triple
T4818311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Elizabeth II Bridge |
E107644
|
entity |
| Predicate | isMajorLinkIn |
P32978
|
FINISHED |
| Object | London’s orbital route |
—
|
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: London’s orbital route | Statement: [Queen Elizabeth II Bridge, isMajorLinkIn, London’s orbital route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorLinkIn Context triple: [Queen Elizabeth II Bridge, isMajorLinkIn, London’s orbital route]
-
A.
isMajorLinkBetween
chosen
Indicates that one entity serves as a primary or most significant connecting link between two or more other entities.
-
B.
isMajorRouteFor
Indicates that something serves as a primary or heavily used pathway or channel for the movement or flow of something else.
-
C.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
D.
isMajorIndexOf
Indicates that one entity serves as the primary or major index reference for locating, organizing, or identifying another entity.
-
E.
isMajorBaseIn
Indicates that a location serves as a primary or central base of operations within a specified area or organization.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1dfa3481909d240d50ed0ee38c |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.