Triple
T17004234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayonet Constitution |
E412527
|
entity |
| Predicate | introducedPropertyQualificationsFor |
P55856
|
FINISHED |
| Object | voters |
—
|
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: voters | Statement: [Bayonet Constitution, introducedPropertyQualificationsFor, voters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedPropertyQualificationsFor Context triple: [Bayonet Constitution, introducedPropertyQualificationsFor, voters]
-
A.
introducedProvision
chosen
Indicates that an entity formally brought a specific provision, clause, or measure into effect or into consideration.
-
B.
providedQualificationFor
Indicates that one entity supplied or granted a qualification, credential, or certification that another entity possesses or uses.
-
C.
eligibleProperties
Indicates that certain properties meet the required conditions or criteria to qualify for a specified purpose or status.
-
D.
usedToQualify
Indicates that one entity serves as a qualifier or modifier that restricts, specifies, or refines the meaning or scope of another entity.
-
E.
introducedAfter
Indicates that one entity was introduced at a later time or stage than 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d380f968819097b59e7bac333ea4 |
completed | April 18, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.