Triple
T29870634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boletaria |
E758585
|
entity |
| Predicate | overrunBy |
P85045
|
FINISHED |
| Object | demons |
—
|
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: demons | Statement: [Boletaria, overrunBy, demons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overrunBy Context triple: [Boletaria, overrunBy, demons]
-
A.
eventuallyOverrunBy
chosen
Indicates that one entity is ultimately defeated, overwhelmed, or taken over by another entity or force after some passage of time.
-
B.
oversLimit
Indicates that an entity exceeds a specified limit, threshold, or allowed maximum.
-
C.
overtook
Indicates that one entity moved past and ahead of another that was previously in front, typically while both were in motion.
-
D.
blowsOver
Indicates that one entity is toppled or knocked down by the force or movement of another entity.
-
E.
holdsOver
Indicates that a certain condition, state, or relationship remains valid or continues to apply across a specified period, context, or range.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676c577fc819089d5842f5edc4148 |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:53 p.m.