Triple
T8327312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soulbury Constitution |
E194985
|
entity |
| Predicate | didNotProvideFor |
P8829
|
FINISHED |
| Object | federalism |
—
|
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: federalism | Statement: [Soulbury Constitution, didNotProvideFor, federalism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: didNotProvideFor Context triple: [Soulbury Constitution, didNotProvideFor, federalism]
-
A.
didNotHold
chosen
Indicates that an expected event, condition, or relationship failed to occur or be valid.
-
B.
doesNotAutomaticallyProvide
Indicates that something is not supplied or made available by default and requires an explicit action or request to be provided.
-
C.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
D.
doesNotHave
Indicates that one entity lacks, is missing, or is not in possession of another entity or attribute.
-
E.
didNotBecome
Indicates that an expected or potential change of state, role, or condition between entities did not occur.
- 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f80ed288190b300e18b9bc58824 |
completed | March 31, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:56 p.m.