Triple
T36637648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EUAA |
E904504
|
entity |
| Predicate | predecessorAgencyBecame |
P162070
|
FINISHED |
| Object | EASO became EUAA |
—
|
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: EASO became EUAA | Statement: [EUAA, predecessorAgencyBecame, EASO became EUAA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAgencyBecame Context triple: [EUAA, predecessorAgencyBecame, EASO became EUAA]
-
A.
isFormerAgencyOf
Indicates that one entity previously functioned as an agency or subordinate body of another entity, but no longer holds that status.
-
B.
supersedingAgency
chosen
Indicates that one agency has replaced or taken over the responsibilities of another agency.
-
C.
formerOrganization
Indicates that an entity was previously affiliated with or employed by a given organization, but is no longer associated with it.
-
D.
employerPredecessorName
Indicates that the referenced name identifies a previous employer of the entity in question.
-
E.
predecessorCompany
Indicates that one company previously existed in a role or form that was succeeded or replaced by another company.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 3, 2026, 4:11 p.m.