Triple
T14728514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | True Cross |
E346005
|
entity |
| Predicate | contestedAspect |
P14608
|
FINISHED |
| Object | authenticity of surviving fragments |
—
|
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 of surviving fragments | Statement: [True Cross, contestedAspect, authenticity of surviving fragments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestedAspect Context triple: [True Cross, contestedAspect, authenticity of surviving fragments]
-
A.
disputedAspect
chosen
Indicates that a particular feature, detail, or component of something is subject to disagreement or contention between parties.
-
B.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
C.
hasControversialAspect
Indicates that something includes an element, feature, or aspect that is disputed, debated, or likely to cause disagreement or public criticism.
-
D.
contestedAt
Indicates that an event, claim, or outcome is being challenged or disputed at a particular time or place.
-
E.
contention
Indicates a state of active disagreement, dispute, or conflict between entities over an issue, claim, or resource.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec26179688190ba9f3cd045da0e2a |
completed | April 14, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.