Triple
T24993465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiscal Compact |
E625505
|
entity |
| Predicate | hasNonSignatory |
P6228
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [Fiscal Compact, hasNonSignatory, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNonSignatory Context triple: [Fiscal Compact, hasNonSignatory, United Kingdom]
-
A.
hasSignatories
Indicates that one or more parties have formally signed or endorsed an agreement, document, or instrument.
-
B.
nonSignatoryParty
chosen
Indicates that an entity is a party related to an agreement or treaty without having formally signed or acceded to it.
-
C.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
D.
initialSignatoriesIncluded
Indicates that the specified entities were part of the original group that formally signed or endorsed an agreement or document.
-
E.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 18, 2026, 6:04 a.m.