Triple
T26874065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khidr |
E676695
|
entity |
| Predicate | performedAct |
P2297
|
FINISHED |
| Object | damaged a boat to protect its owners from a tyrant |
—
|
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: damaged a boat to protect its owners from a tyrant | Statement: [Khidr, performedAct, damaged a boat to protect its owners from a tyrant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedAct Context triple: [Khidr, performedAct, damaged a boat to protect its owners from a tyrant]
-
A.
performed
chosen
Indicates that an entity carried out, executed, or conducted a specific action, task, or activity.
-
B.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
-
C.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
D.
depictedPerforming
Indicates that one entity is shown or illustrated as carrying out an action or activity.
-
E.
performedFrom
Indicates that an action or operation is carried out starting at or originating from a specified source location, context, or 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 5:34 a.m.