Triple
T25749657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | statue of William IV |
E648439
|
entity |
| Predicate | reasonForNotBeingBuilt |
P36021
|
FINISHED |
| Object | insufficient funds |
—
|
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: insufficient funds | Statement: [statue of William IV, reasonForNotBeingBuilt, insufficient funds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForNotBeingBuilt Context triple: [statue of William IV, reasonForNotBeingBuilt, insufficient funds]
-
A.
reasonForNoProduction
chosen
Indicates the specific cause or explanation for why production did not occur.
-
B.
reasonForNonInstallation
Indicates the explanation or cause for why an expected installation did not occur.
-
C.
builtWithout
Indicates that something was constructed or created in the absence of a particular component, material, tool, or condition.
-
D.
reasonForNotCompletion
Indicates the explanation or cause for why a task, process, or obligation was not completed.
-
E.
reasonForMissingFeature
Indicates the explanation or cause for why a particular feature is absent or not implemented.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 22, 2026, 4:33 a.m.