Triple
T5224081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganina Yama |
E117940
|
entity |
| Predicate | hasRelicsStatus |
P62129
|
FINISHED |
| Object | place of veneration of royal martyrs |
—
|
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: place of veneration of royal martyrs | Statement: [Ganina Yama, hasRelicsStatus, place of veneration of royal martyrs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelicsStatus Context triple: [Ganina Yama, hasRelicsStatus, place of veneration of royal martyrs]
-
A.
containsRelic
Indicates that one entity holds, includes, or has within it a relic.
-
B.
hasHeirloom
Indicates that one entity possesses or is associated with an heirloom originating from another entity.
-
C.
isRelictLineage
Indicates that an entity represents a surviving remnant of an otherwise extinct evolutionary lineage.
-
D.
hasRitualObject
Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
-
E.
hasIconicArtifact
Indicates that an entity possesses or is associated with a distinctive, emblematic artifact that represents its identity, history, or significance.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7abd3ed48190bfd8d2f2ca399741 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78a89b608190b259d3d8658f8f7c |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:48 p.m.