Triple
T36638168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reitox |
E904515
|
entity |
| Predicate | linkedToAgency |
P102203
|
FINISHED |
| Object | EMCDDA |
—
|
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: EMCDDA | Statement: [Reitox, linkedToAgency, EMCDDA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToAgency Context triple: [Reitox, linkedToAgency, EMCDDA]
-
A.
partnerAgency
Indicates a formal collaborative relationship in which one agency acts as a partner to another agency.
-
B.
belongsToAgency
Indicates that an entity is under the authority, control, or affiliation of a specific agency.
-
C.
isAgencyFor
Indicates that one entity functions as an agent or representative acting on behalf of another entity.
-
D.
relevantAgency
chosen
Indicates that an agency has authority, responsibility, or significant involvement in relation to a particular matter, entity, or action.
-
E.
customerAgency
Indicates a relationship where one party (the customer) authorizes or is represented by another party (the agency) to act on their behalf in transactions or decisions.
- 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_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 3, 2026, 4:11 p.m.