Triple
T29208692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of 1864 |
E740487
|
entity |
| Predicate | strengthenedBranch |
P166427
|
FINISHED |
| Object | executive |
—
|
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 | Statement: [Constitution of 1864, strengthenedBranch, executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthenedBranch Context triple: [Constitution of 1864, strengthenedBranch, executive]
-
A.
supportingBranch
Indicates that one branch structurally or functionally supports another branch.
-
B.
trainedBranch
Indicates that one entity has provided training or instruction to a specific branch or subdivision of another entity.
-
C.
representedBranch
Indicates that one entity serves as a representative or proxy for a particular branch of another entity or organization.
-
D.
affectedBranch
Indicates that one entity is a branch that is impacted or influenced by the state or actions associated with another entity.
-
E.
strengthenedAfter
Indicates that one entity becomes stronger or more robust as a result of something that occurs after a specified event or condition involving another entity.
- F. None of above. chosen
Provenance (4 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66403fce48190817d399195f1339a |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65fb2ead08190b06677d4d6ea1ea8 |
completed | May 2, 2026, 8:33 p.m. |
Created at: April 28, 2026, 12:10 p.m.