Triple
T217382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antarctic Treaty System |
E4135
|
entity |
| Predicate | hasPartyType |
P6384
|
FINISHED |
| Object | consultative parties |
—
|
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: consultative parties | Statement: [Antarctic Treaty System, hasPartyType, consultative parties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartyType Context triple: [Antarctic Treaty System, hasPartyType, consultative parties]
-
A.
hasMemberParty
Indicates that a group, organization, or coalition includes a specific party as one of its members.
-
B.
participantType
chosen
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
C.
typicalParty
Indicates that an entity is a usual, standard, or characteristic participant in a given type of event, situation, or relationship.
-
D.
hasParticleType
Indicates that an entity is associated with, composed of, or characterized by a specific type or category of particle.
-
E.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c5062e48190833be10e4770e1e9 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5357bc8190b29a48e3053fb76d |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.