Triple
T343723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican Constitution of 1824 |
E6892
|
entity |
| Predicate | establishedBranch |
P5762
|
FINISHED |
| Object | executive branch |
—
|
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: executive branch | Statement: [Mexican Constitution of 1824, establishedBranch, executive branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedBranch Context triple: [Mexican Constitution of 1824, establishedBranch, executive branch]
-
A.
servesBranch
Indicates that one entity provides services or support to a particular branch or subdivision of an organization.
-
B.
establishedAs
chosen
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
C.
establishedOffice
Indicates that an entity created or set up an official office or place of operation.
-
D.
establishedAt
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
E.
establishedFollowing
Indicates that one entity created or set up another entity after, and in consequence of, a prior entity or event.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb0019088190a9b969c4287dc4fa |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e9530c98819085025efe4e04aa7e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.