Triple
T27915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .cl |
E557
|
entity |
| Predicate | disputePolicy |
P2159
|
FINISHED |
| Object | local arbitration procedures |
—
|
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: local arbitration procedures | Statement: [.cl, disputePolicy, local arbitration procedures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputePolicy Context triple: [.cl, disputePolicy, local arbitration procedures]
-
A.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
B.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
-
C.
officeContested
Indicates that a particular office or position is being actively sought or challenged by multiple parties in an election or selection process.
-
D.
agreement
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
-
E.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
- F. None of above. chosen
Provenance (4 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24925607c8190a9ce7ec834f3e5bb |
completed | Feb. 28, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69a2486bd74c81908d32be3c7d22f51f |
completed | Feb. 28, 2026, 1:44 a.m. |
| PDg | Predicate description generation | batch_69a249246968819099985f13127063d2 |
completed | Feb. 28, 2026, 1:47 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.