Triple
T26351962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Ascetics |
E662924
|
entity |
| Predicate | firstUnderstood |
P4732
|
FINISHED |
| Object | Four Noble Truths |
—
|
NE NERFINISHED |
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: Four Noble Truths | Statement: [Five Ascetics, firstUnderstood, Four Noble Truths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUnderstood Context triple: [Five Ascetics, firstUnderstood, Four Noble Truths]
-
A.
firstOrdinary
Indicates that the subject is the first entity to hold or occupy an ordinary (non-special, standard) position, role, or status in a given sequence or context.
-
B.
firstIndication
Indicates that something is the earliest or initial sign, symptom, or evidence pointing to a particular condition, event, or state.
-
C.
firstStandard
Indicates that the subject is the earliest or primary instance in a defined standard, sequence, or set of reference criteria.
-
D.
recognizedFirstBy
chosen
Indicates that one entity was the earliest or initial recognizer, identifier, or acknowledger of another entity.
-
E.
firstObjectDiscovered
Indicates that the referenced object is the earliest one identified or detected in a given context or sequence.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: April 26, 2026, 10:46 p.m.