Triple
T4759770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown of Thorns |
E105671
|
entity |
| Predicate | hasRelicTradition |
P46023
|
FINISHED |
| Object | Crown of Thorns relic in Paris |
—
|
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: Crown of Thorns relic in Paris | Statement: [Crown of Thorns, hasRelicTradition, Crown of Thorns relic in Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelicTradition Context triple: [Crown of Thorns, hasRelicTradition, Crown of Thorns relic in Paris]
-
A.
containsRelic
Indicates that one entity holds, includes, or has within it a relic.
-
B.
hasStatusInTradition
Indicates that an entity holds a particular recognized status or standing within a specified tradition or traditional framework.
-
C.
hasTraditionIn
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
D.
variantTraditions
chosen
Indicates that there exist differing or alternative traditions or customary practices associated with the same subject or context.
-
E.
isRelictLineage
Indicates that an entity represents a surviving remnant of an otherwise extinct evolutionary lineage.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650dc7fc81909b483ef3c456ae0d |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.