Triple
T16965826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALENA |
E411536
|
entity |
| Predicate | hasDisputeSettlementMechanism |
P125340
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ALENA, hasDisputeSettlementMechanism, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisputeSettlementMechanism Context triple: [ALENA, hasDisputeSettlementMechanism, true]
-
A.
hasDisputeRegime
chosen
Indicates that there exists a specific dispute-handling framework, system, or set of rules governing how disputes related to the subject are managed or resolved.
-
B.
hasDisputeWith
Indicates that there is a conflict, disagreement, or contested issue between two entities.
-
C.
hasDisputeResolutionBody
Indicates that there exists a designated body or authority responsible for resolving disputes related to the associated entity or relationship.
-
D.
hasDisputeType
Indicates that an entity is associated with a particular category or type of dispute.
-
E.
disputeSettlementArm
Indicates a relationship where an entity functions as the division, branch, or mechanism responsible for handling, managing, or resolving disputes or conflicts for 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0a3cecc8190a490573adce80cca |
completed | April 18, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:31 a.m.