Triple
T15680967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Nails |
E377573
|
entity |
| Predicate | historicityView |
P59206
|
FINISHED |
| Object | authenticity disputed by 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: authenticity disputed by historians | Statement: [Holy Nails, historicityView, authenticity disputed by historians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicityView Context triple: [Holy Nails, historicityView, authenticity disputed by historians]
-
A.
historicityDebate
chosen
Indicates a debate or scholarly dispute over whether an event, figure, or narrative is historically factual or actually occurred.
-
B.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
C.
hasHistoricity
Indicates that something possesses historical existence, significance, or authenticity, rather than being purely fictional, mythical, or timeless.
-
D.
historicalSee
Indicates that one entity observed, encountered, or took visual notice of another entity in the past.
-
E.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f306a1c8190a819541a3cc51f5a |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.