Triple
T11662317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibraltar Constitution Order 2006 |
E277152
|
entity |
| Predicate | reservesToUK |
P100853
|
FINISHED |
| Object | defence |
—
|
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: defence | Statement: [Gibraltar Constitution Order 2006, reservesToUK, defence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservesToUK Context triple: [Gibraltar Constitution Order 2006, reservesToUK, defence]
-
A.
reserves
Indicates that an entity has arranged in advance to hold or secure something for future use or access.
-
B.
locatedInBritishCountry
Indicates that one entity is geographically or administratively situated within a country that is part of the United Kingdom.
-
C.
suspendedInUK
Indicates that an entity’s operations, activities, or status have been formally halted or put on hold within the United Kingdom.
-
D.
statusInUK
Indicates the legal or official status that an entity holds within the United Kingdom (e.g., immigration, residency, or authorization category).
-
E.
broadcastInUnitedKingdomBy
Indicates that something (such as a program or event) is or was broadcast by a particular broadcaster within the United Kingdom.
- F. None of above. chosen
Provenance (4 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d29fdc8190af46b6e2badb1df5 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:39 p.m.