Triple
T33319429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thundering Legion |
E853097
|
entity |
| Predicate | historicityOfMiracle |
P201440
|
FINISHED |
| Object | disputed by modern historians |
—
|
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: disputed by modern historians | Statement: [Thundering Legion, historicityOfMiracle, disputed by modern historians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicityOfMiracle Context triple: [Thundering Legion, historicityOfMiracle, disputed by modern historians]
-
A.
historicityOfPersecution
Indicates that there is documented or evidenced historical persecution involving the related entities.
-
B.
historicalBelief
Indicates that an entity holds or held a belief, view, or conviction at some point in the past.
-
C.
miracleDescription
Indicates that a miraculous event or phenomenon is being described or characterized.
-
D.
recognizedAsMiraculous
Indicates that something is acknowledged or officially deemed to be miraculous, often by an authority or community.
-
E.
historicalExistence
Indicates that an entity actually existed at some point in real-world history, as opposed to being fictional, hypothetical, or mythological.
- F. None of above. chosen
Provenance (4 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fff59a00a881909b35b799654b3c45 |
completed | May 10, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69fff4d0a2e081909c972189b33d0128 |
completed | May 10, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69fff59875cc8190864864e951951679 |
completed | May 10, 2026, 3:03 a.m. |
Created at: May 1, 2026, 1:33 a.m.