Triple
T24993605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two-Pack legislation |
E625509
|
entity |
| Predicate | wasAdoptedAfter |
P6513
|
FINISHED |
| Object | eurozone sovereign debt crisis |
—
|
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: eurozone sovereign debt crisis | Statement: [Two-Pack legislation, wasAdoptedAfter, eurozone sovereign debt crisis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAdoptedAfter Context triple: [Two-Pack legislation, wasAdoptedAfter, eurozone sovereign debt crisis]
-
A.
adoptedAfter
chosen
Indicates that one entity was adopted at a later time than another entity.
-
B.
readoptedOn
Indicates the date or time at which something that was previously adopted is formally adopted again.
-
C.
adoptedAt
Indicates the time or date at which an adoption event took place.
-
D.
officialAdoptionYear
Indicates the year in which something (such as a policy, standard, symbol, or practice) was formally adopted or officially put into use.
-
E.
givenInAdoptionBy
Indicates that an entity was transferred into adoption through the action or decision of a specific giver (such as a person or organization).
- 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_69f44a4787948190874b230f692d16c7 |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:04 a.m.