Triple
T31729054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spear of Longinus |
E809804
|
entity |
| Predicate | certaintyOfHistoricalExistence |
P33842
|
FINISHED |
| Object | disputed |
—
|
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 | Statement: [Spear of Longinus, certaintyOfHistoricalExistence, disputed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: certaintyOfHistoricalExistence Context triple: [Spear of Longinus, certaintyOfHistoricalExistence, disputed]
-
A.
historicalExistence
Indicates that an entity actually existed at some point in real-world history, as opposed to being fictional, hypothetical, or mythological.
-
B.
hasUncertainHistoricBasis
chosen
Indicates that the historical foundation or authenticity of the related fact, event, or relationship is doubtful, disputed, or not firmly established.
-
C.
historicalEvidence
Indicates that there exists documented or otherwise verifiable information supporting the occurrence, authenticity, or truth of a past event, state, or relationship between entities.
-
D.
chronologyCertainty
Indicates the degree of confidence or uncertainty about the ordering or dating of events or temporal relationships.
-
E.
namedInHistoricalSources
Indicates that an entity is explicitly mentioned or identified in historical documents or records.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab1d46a4819098cbd250564c7d85 |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:21 p.m.