Triple
T8213215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Array |
E191870
|
entity |
| Predicate | planningConsentGranted |
P32451
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [London Array, planningConsentGranted, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningConsentGranted Context triple: [London Array, planningConsentGranted, 2006]
-
A.
grantedIn
Indicates that something (such as a right, status, or permission) is formally conferred or authorized within a particular context, document, or jurisdiction.
-
B.
grantedBy
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
-
C.
grantedStatus
chosen
Indicates that an entity has been officially approved or given a particular status, permission, or privilege.
-
D.
grantedWith
Indicates that one entity is given, conferred, or endowed together with another entity as part of the same granting event or condition.
-
E.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76e1ffa081908883338e7d3a7c6d |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:44 p.m.