Triple
T11826058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Arya Truths |
E281262
|
entity |
| Predicate | secondTruthName |
P101702
|
FINISHED |
| Object | samudaya |
—
|
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: samudaya | Statement: [Four Arya Truths, secondTruthName, samudaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondTruthName Context triple: [Four Arya Truths, secondTruthName, samudaya]
-
A.
secondGenerationName
Indicates that the object is the name given to the second generation derived from the subject.
-
B.
secondHolderGivenName
Indicates that the given name specified belongs to the second holder in a multi-holder relationship or record.
-
C.
secondCreatedBy
Indicates that an entity was created by a second or subsequent creator, distinguishing this creator from the primary or original one.
-
D.
secondWord
Indicates that one entity is the second word in sequence immediately following the first entity in a text or utterance.
-
E.
secondClauseKnownAs
Indicates that one clause in a legal or formal document is alternatively referred to or identified by a second, specific name or designation.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5eb299481909de3c0e85628fbe4 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.