Triple
T28066543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specialised Committee on Gibraltar |
E709265
|
entity |
| Predicate | isJointBodyOf |
P163441
|
FINISHED |
| Object | European Union |
—
|
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: European Union | Statement: [Specialised Committee on Gibraltar, isJointBodyOf, European Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isJointBodyOf Context triple: [Specialised Committee on Gibraltar, isJointBodyOf, European Union]
-
A.
isJointBodyOf
chosen
Indicates that an entity is a composite or shared governing or administrative body formed jointly by two or more other entities.
-
B.
isPartOfBodyWithNumberOfMembers
Indicates that something is a component of a body or group that consists of a specified number of members.
-
C.
isJointBase
Indicates that two or more components share a common base or foundation point.
-
D.
isExtremityOf
Indicates that one entity is an outermost part, boundary, or terminal point of another entity.
-
E.
isBackboneOf
Indicates that one entity forms the main supporting structure or central framework upon which another entity fundamentally depends.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6401c365c8190bf95e0e5c1f94021 |
completed | May 2, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:43 p.m.