Triple
T139308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of California |
E2816
|
entity |
| Predicate | establishesBranch |
P986
|
FINISHED |
| Object | executive branch of California |
—
|
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 of California | Statement: [Constitution of California, establishesBranch, executive branch of California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishesBranch Context triple: [Constitution of California, establishesBranch, executive branch of California]
-
A.
establishes
chosen
Indicates that one entity initiates, creates, or formally sets up another entity, relationship, or state, often giving it official or recognized status.
-
B.
servesBranch
Indicates that one entity provides services or support to a particular branch or subdivision of an organization.
-
C.
createdAgency
Indicates that one entity brought an agency into existence, establishing it as a new organizational or institutional body.
-
D.
serviceBranch
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
E.
establishedOffice
Indicates that an entity created or set up an official office or place of operation.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257c679d88190bc71775dab2cfc64 |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a2565426c08190aab68e34a6a2d60e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.