Triple
T19020183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indo-European mythology |
E465461
|
entity |
| Predicate | hasKeyTheory |
P133584
|
FINISHED |
| Object | trifunctional hypothesis |
—
|
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: trifunctional hypothesis | Statement: [Indo-European mythology, hasKeyTheory, trifunctional hypothesis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyTheory Context triple: [Indo-European mythology, hasKeyTheory, trifunctional hypothesis]
-
A.
hasKeyTheorem
Indicates that one entity contains, relies on, or is characterized by a central or foundational theorem associated with the other entity.
-
B.
hasKeyPass
Indicates that an entity possesses or is granted a key-based pass that allows access or authorization to something.
-
C.
hasKeyElement
Indicates that one entity contains or depends on another entity that serves as a primary or essential component.
-
D.
hasKeyFunction
Indicates that one entity serves as a primary or essential function or role for another entity.
-
E.
hasKeyStep
Indicates that one action, event, or process includes another as a crucial or essential intermediate step.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6de93408190a98dea2319f1af62 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8f6f7c8190af645bf08823ee2b |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:02 p.m.