Triple
T25789661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union (Amendment) Act 2008 |
E649514
|
entity |
| Predicate | implementedTreaty |
P133400
|
FINISHED |
| Object | Treaty of Lisbon |
—
|
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: Treaty of Lisbon | Statement: [European Union (Amendment) Act 2008, implementedTreaty, Treaty of Lisbon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedTreaty Context triple: [European Union (Amendment) Act 2008, implementedTreaty, Treaty of Lisbon]
-
A.
treatyImplemented
chosen
Indicates that the terms or provisions of a treaty have been put into effect or carried out in practice between the relevant parties.
-
B.
confirmedTreaty
Indicates that an entity has formally approved, ratified, or validated a treaty, making the agreement officially recognized or in force.
-
C.
treatyConcluded
Indicates that a formal agreement or treaty has been officially finalized and brought into force between the involved parties.
-
D.
resultOfTreaties
Indicates that something exists, occurs, or holds true as a consequence or outcome of one or more treaties.
-
E.
treatyAfter
Indicates that a treaty or formal agreement was established after a specified prior event, condition, or relationship between the entities.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603bb02288190b40cedbed5b9651d |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 5:58 a.m.