Triple
T8058273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dasein (Heidegger) |
E188052
|
entity |
| Predicate | hasOntologicalPriorityOver |
P1616
|
FINISHED |
| Object | other beings |
—
|
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: other beings | Statement: [Dasein (Heidegger), hasOntologicalPriorityOver, other beings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOntologicalPriorityOver Context triple: [Dasein (Heidegger), hasOntologicalPriorityOver, other beings]
-
A.
protégéOf
Indicates that one entity is mentored, trained, or guided in their development by another, more experienced entity.
-
B.
isBackboneOf
Indicates that one entity forms the main supporting structure or central framework upon which another entity fundamentally depends.
-
C.
confersPrecedenceIn
chosen
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
-
D.
predecessorInConcept
Indicates that one concept temporally or logically comes before another in a sequence or developmental progression.
-
E.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
- 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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fa51adc8190b9327441bd8b9fb3 |
completed | March 31, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:25 p.m.