Triple
T33784499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Familia |
E865749
|
entity |
| Predicate | supportedReformType |
P194061
|
FINISHED |
| Object | constitutional reform |
—
|
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: constitutional reform | Statement: [Familia, supportedReformType, constitutional reform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedReformType Context triple: [Familia, supportedReformType, constitutional reform]
-
A.
supportsReformType
chosen
Indicates that one entity endorses, advocates for, or is in favor of a particular type or category of reform associated with another entity.
-
B.
supportedReformer
Indicates that one entity actively endorsed or backed a particular reformer in their efforts or cause.
-
C.
canReform
Indicates that an entity has the ability or potential to change, improve, or be corrected from a previous state, behavior, or condition.
-
D.
subjectToReformBy
Indicates that an entity is undergoing or designated for changes, improvements, or restructuring carried out by another entity.
-
E.
reformsBy
Indicates that one entity initiates, implements, or is responsible for changes or improvements (reforms) affecting 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:45 a.m.