Triple
T6188086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaisesika |
E138113
|
entity |
| Predicate | acceptsSubstance |
P69565
|
FINISHED |
| Object | earth |
—
|
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: earth | Statement: [Vaisesika, acceptsSubstance, earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptsSubstance Context triple: [Vaisesika, acceptsSubstance, earth]
-
A.
usedSubstance
Indicates that an entity has consumed, applied, or otherwise made use of a particular substance.
-
B.
associatedWithSubstance
Indicates that one entity has a relevant connection or involvement with a particular substance, such as use, presence, exposure, or composition.
-
C.
hasAddictiveSubstance
Indicates that an entity contains or involves a substance capable of causing addiction in those who use or consume it.
-
D.
hasAddictionPotential
Indicates that one entity (typically a substance or activity) has the capacity to cause another entity (typically a person) to develop dependence or addictive behavior toward it.
-
E.
hasFictionalSubstance
Indicates that one entity includes, contains, or involves a fictional or imaginary substance as part of its composition, setting, or narrative.
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06217be288190997032c8c4839fa5 |
completed | March 22, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:19 p.m.