Triple
T14456221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priory of Sion |
E358464
|
entity |
| Predicate | debunkedBy |
P114721
|
FINISHED |
| Object | 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: historians | Statement: [Priory of Sion, debunkedBy, historians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: debunkedBy Context triple: [Priory of Sion, debunkedBy, historians]
-
A.
repudiatedOn
Indicates the specific date or time at which something (such as a claim, agreement, or association) was formally rejected, disowned, or renounced.
-
B.
repudiatedAfter
Indicates that one entity formally rejects, disavows, or withdraws support for another entity after a specified time or subsequent event.
-
C.
debatedWithin
Indicates that something is discussed or argued about within a particular group, context, or domain.
-
D.
derogadaPor
Indicates that a law, rule, or norm has been annulled, revoked, or rendered invalid by another legal provision or authority.
-
E.
debatedAs
Indicates that one entity is discussed or argued over in terms of being equivalent to, or serving in the role of, another entity within a debate or comparative argument.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91a9c0d48190ae015e5e0db806ca |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:19 a.m.