Triple
T859185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brahman |
E18561
|
entity |
| Predicate | equatedWith |
P6530
|
FINISHED |
| Object | ultimate cause of the universe |
—
|
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: ultimate cause of the universe | Statement: [Brahman, equatedWith, ultimate cause of the universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equatedWith Context triple: [Brahman, equatedWith, ultimate cause of the universe]
-
A.
equivalentTo
chosen
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
-
B.
coincidesWith
Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
-
C.
reconciledWith
Indicates that two previously conflicting or estranged entities have resolved their differences and restored a state of agreement or harmony with each other.
-
D.
hasEquivalent
Indicates that two entities are considered equal in value, meaning, or function within a given context.
-
E.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
- 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.