Triple
T12985483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troezen Constitution |
E321755
|
entity |
| Predicate | definedBranch |
P18917
|
FINISHED |
| Object | executive power |
—
|
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 power | Statement: [Troezen Constitution, definedBranch, executive power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedBranch Context triple: [Troezen Constitution, definedBranch, executive power]
-
A.
definesBranch
chosen
Indicates that one entity specifies or establishes a particular branch or subdivision of another entity.
-
B.
representedBranch
Indicates that one entity serves as a representative or proxy for a particular branch of another entity or organization.
-
C.
trainedBranch
Indicates that one entity has provided training or instruction to a specific branch or subdivision of another entity.
-
D.
addressedBranch
Indicates that an action, communication, or item is specifically directed to or associated with a particular branch of an organization or network.
-
E.
possibleBranch
Indicates that one entity can serve as an alternative or potential continuation path branching from another entity.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:40 p.m.