Triple
T21843906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Beloved (Rumi) |
E539323
|
entity |
| Predicate | modeOfPresence |
P31835
|
FINISHED |
| Object | experienced inwardly |
—
|
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: experienced inwardly | Statement: [the Beloved (Rumi), modeOfPresence, experienced inwardly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modeOfPresence Context triple: [the Beloved (Rumi), modeOfPresence, experienced inwardly]
-
A.
typeOfPresence
chosen
Indicates the manner or mode in which an entity is present or exists in relation to another entity, context, or environment.
-
B.
modernPresence
Indicates that something exists, appears, or is active in the contemporary or present-day context.
-
C.
traditionalPresenceIn
Indicates that an entity has a customary or historically established presence within a particular place, context, or setting.
-
D.
mediaPresence
Indicates the extent to which something is visible, represented, or covered within various media channels or platforms.
-
E.
statePresence
Indicates that an entity exists, operates, or is present within a particular state or governmental jurisdiction.
- 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_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. |
Created at: April 16, 2026, 6:55 p.m.