Triple
T29208693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of 1864 |
E740487
|
entity |
| Predicate | weakenedBranch |
P53512
|
FINISHED |
| Object | legislature |
—
|
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: legislature | Statement: [Constitution of 1864, weakenedBranch, legislature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weakenedBranch Context triple: [Constitution of 1864, weakenedBranch, legislature]
-
A.
weakenedDuring
Indicates that an entity’s strength, intensity, or effectiveness is reduced over the course of a specified time period or event.
-
B.
weakerThan
Indicates that one entity has less strength, power, or effectiveness than another entity.
-
C.
victimBranch
Indicates that one branch or subdivision is the target or sufferer of a harmful, adverse, or exploitative action carried out by another entity.
-
D.
possibleBranch
Indicates that one entity can serve as an alternative or potential continuation path branching from another entity.
-
E.
affectedBranch
chosen
Indicates that one entity is a branch that is impacted or influenced by the state or actions associated with 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_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. |
Created at: April 28, 2026, 12:10 p.m.