Triple
T21843886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Beloved (Rumi) |
E539323
|
entity |
| Predicate | relationshipToRumi |
P145533
|
FINISHED |
| Object | object of longing |
—
|
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: object of longing | Statement: [the Beloved (Rumi), relationshipToRumi, object of longing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToRumi Context triple: [the Beloved (Rumi), relationshipToRumi, object of longing]
-
A.
relationshipToRama
Indicates the specific familial, social, or other relational connection that an entity has to Rama.
-
B.
relationshipToRa
Indicates a specified type of relational connection that an entity has to the entity Ra.
-
C.
relationshipToMonk
Indicates the specific type of relationship an entity has to a monk, such as familial, social, or institutional connection.
-
D.
relationshipToSita
Indicates the specific familial, social, or interpersonal relationship that one entity has to Sita.
-
E.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0bd5248f08190ba208512eafbe7ad |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c187bc548190b4ca13150f6bae38 |
completed | April 21, 2026, 12:15 a.m. |
Created at: April 16, 2026, 6:55 p.m.