Triple
T23476437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cantonal courts of Ecuador |
E570275
|
entity |
| Predicate | partyToProceedings |
P15954
|
FINISHED |
| Object | individuals |
—
|
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: individuals | Statement: [cantonal courts of Ecuador, partyToProceedings, individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyToProceedings Context triple: [cantonal courts of Ecuador, partyToProceedings, individuals]
-
A.
partyToCase
chosen
Indicates that an entity is involved in a legal case as one of its formal participants (e.g., plaintiff, defendant, or other party).
-
B.
typeOfProceedings
Indicates the specific category or kind of legal or formal process under which an action or case is being conducted.
-
C.
scriptUsedForProceedings
Indicates that a particular writing system or script is used to record, document, or conduct the referenced proceedings.
-
D.
partiesAre
Indicates that certain entities are the participants or sides involved in a particular relationship, agreement, or event.
-
E.
hearsProceedingsBroughtBy
Indicates that a judicial or administrative body formally considers and adjudicates legal proceedings initiated by a particular party.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a74cf57081909d2b90a806d68c08 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:01 p.m.