Triple
T992052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanuman |
E21412
|
entity |
| Predicate | performedDeed |
P2297
|
FINISHED |
| Object | leaping across the ocean to Lanka |
—
|
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: leaping across the ocean to Lanka | Statement: [Hanuman, performedDeed, leaping across the ocean to Lanka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedDeed Context triple: [Hanuman, performedDeed, leaping across the ocean to Lanka]
-
A.
performed
chosen
Indicates that an entity carried out, executed, or conducted a specific action, task, or activity.
-
B.
notableWorkPerformed
Indicates that an entity has created, executed, or contributed significantly to a particular work that is recognized as notable or important.
-
C.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
D.
undertook
Indicates that an entity assumed responsibility for starting and carrying out a task, project, or action.
-
E.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4c25e5081909ff1ada6b8bf617a |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2adbde48190b07966d0c3179516 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.