Triple
T859423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vedanta |
E18566
|
entity |
| Predicate | systematizes |
P123
|
FINISHED |
| Object | Upanishadic philosophy |
—
|
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: Upanishadic philosophy | Statement: [Vedanta, systematizes, Upanishadic philosophy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systematizes Context triple: [Vedanta, systematizes, Upanishadic philosophy]
-
A.
systematicsNote
Indicates that there is an associated comment or annotation concerning the classification or systematic arrangement of the entities involved.
-
B.
classificationSystem
Indicates a relationship where an entity is organized or categorized according to a particular classification scheme or taxonomy.
-
C.
system
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
-
D.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
E.
organizes
chosen
Indicates that one entity arranges, coordinates, or structures activities, items, or people into an ordered or planned form for a particular purpose.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac50e5ec81908ac0c4b7123b4ebb |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.