Triple
T6891062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish language in Ecuador |
E159045
|
entity |
| Predicate | constitutionalRecognition |
P30578
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Spanish language in Ecuador, constitutionalRecognition, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constitutionalRecognition Context triple: [Spanish language in Ecuador, constitutionalRecognition, yes]
-
A.
constitutionalRecognitionYear
Indicates the year in which a constitution formally recognizes or grants status to the referenced entity or concept.
-
B.
recognizedInConstitution
chosen
Indicates that an entity’s status, rights, or role is formally acknowledged and defined within a constitution.
-
C.
independenceRecognized
Indicates that one entity formally acknowledges another entity’s status as independent and self-governing.
-
D.
constitutionalMention
Indicates that something is explicitly referenced or discussed within a constitution or constitutional document.
-
E.
constitutionalSubjectHeading
Indicates that an entity serves as the main constitutional topic or subject focus of another entity (such as a document, case, or discussion).
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d92d45f08190a730b3842c95b521 |
completed | March 27, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.