Triple
T20150598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ṭupṭīkā |
E491423
|
entity |
| Predicate | concernsDebateWith |
P50993
|
FINISHED |
| Object | other Hindu philosophical schools |
—
|
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 Hindu philosophical schools | Statement: [Ṭupṭīkā, concernsDebateWith, other Hindu philosophical schools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsDebateWith Context triple: [Ṭupṭīkā, concernsDebateWith, other Hindu philosophical schools]
-
A.
majorDebateWith
Indicates a significant, often public or formal, debate or dispute occurring between two entities.
-
B.
debateTopic
Indicates that one entity serves as the subject or issue being discussed or argued about in a debate involving another entity.
-
C.
relatedToDebate
chosen
Indicates a relationship in which something is connected or relevant to a debate, discussion, or argumentative exchange.
-
D.
fieldOfDebate
Indicates that something is the subject or domain around which a debate or argumentative discussion is centered.
-
E.
debatedAs
Indicates that one entity is discussed or argued over in terms of being equivalent to, or serving in the role of, another entity within a debate or comparative argument.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667a1c5848190975b17ab07251f8b |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.