Triple
T3479974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyr |
E73465
|
entity |
| Predicate | hasAlternativeParentTraditions |
P49012
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tyr, hasAlternativeParentTraditions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeParentTraditions Context triple: [Tyr, hasAlternativeParentTraditions, yes]
-
A.
hasChildInSomeTraditions
Indicates that, in at least some cultural, religious, or historical traditions, one entity is regarded as the child or offspring of another.
-
B.
hasChildrenInTradition
Indicates that an entity has one or more children specifically within the context of a particular tradition, lineage, or customary framework.
-
C.
traditionInheritedFrom
Indicates that a tradition has been passed down or derived from an earlier source, group, or culture.
-
D.
hasSourceTradition
Indicates that something originates from, or is derived within, a particular cultural, religious, intellectual, or historical tradition.
-
E.
hasTraditionIn
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
- 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb7461708190898002fbd1191f34 |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:17 p.m.