Triple
T24627674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASMA |
E609586
|
entity |
| Predicate | managementPlanApprovedBy |
P807
|
FINISHED |
| Object | Antarctic Treaty Consultative Meeting |
—
|
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: Antarctic Treaty Consultative Meeting | Statement: [ASMA, managementPlanApprovedBy, Antarctic Treaty Consultative Meeting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managementPlanApprovedBy Context triple: [ASMA, managementPlanApprovedBy, Antarctic Treaty Consultative Meeting]
-
A.
approvalProcessManagedBy
Indicates that the responsibility for overseeing and controlling the approval process is assigned to a specific managing entity.
-
B.
approvedBy
chosen
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
C.
approvedAt
Indicates the date and time at which an entity received formal approval.
-
D.
hasManagementPlan
Indicates that an entity is associated with a defined management plan specifying how it should be overseen, maintained, or administered.
-
E.
publicApproval
Indicates the degree to which the general public supports, agrees with, or has a favorable opinion of a person, action, policy, or entity.
- 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.