Triple
T4906501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bharata |
E109923
|
entity |
| Predicate | emotionOnLearningOfExile |
P59360
|
FINISHED |
| Object | grief |
—
|
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: grief | Statement: [Bharata, emotionOnLearningOfExile, grief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emotionOnLearningOfExile Context triple: [Bharata, emotionOnLearningOfExile, grief]
-
A.
causeOfExile
Indicates the reason or circumstance that led to an entity’s exile.
-
B.
wasExiled
Indicates that an entity was forcibly sent away from their home or country, typically as a punishment or due to political or social pressures.
-
C.
traditionallyExiledTo
Indicates that an entity has, by long-standing custom or tradition, been sent away or banished to a particular place.
-
D.
exiledGovernment
Indicates a government that operates in exile, having been forced to leave and function outside its own country while still claiming authority over it.
-
E.
periodOfExile
Indicates a time span during which an entity is banished, expelled, or forced to live away from its native or rightful place.
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e72ed5c819081104c99a398e0af |
completed | March 20, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6cc228088190849f23b7bd4cf549 |
completed | March 20, 2026, 3:50 p.m. |
Created at: March 20, 2026, 1:29 p.m.