Triple
T4513259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian religions |
E102097
|
entity |
| Predicate | shareConcept |
P5696
|
FINISHED |
| Object | samsara (cycle of birth and death) |
—
|
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: samsara (cycle of birth and death) | Statement: [Indian religions, shareConcept, samsara (cycle of birth and death)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareConcept Context triple: [Indian religions, shareConcept, samsara (cycle of birth and death)]
-
A.
share
Indicates that one entity gives, divides, or jointly uses a resource, item, or information with another entity.
-
B.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
C.
sharesMeaningWith
Indicates that two expressions convey the same or very similar meaning, even if they differ in form or wording.
-
D.
sharesMission
Indicates that two or more entities are aligned in purpose, pursuing the same overarching mission or goal.
-
E.
sharesFeatureWith
chosen
Indicates that two entities have at least one common attribute, property, or characteristic in common.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5722d8fc81909c5f2d9a38d17a6b |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.