Triple
T20778294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phineus |
E511410
|
entity |
| Predicate | helpDescription |
P141488
|
FINISHED |
| Object | gave directions to Colchis |
—
|
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: gave directions to Colchis | Statement: [Phineus, helpDescription, gave directions to Colchis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpDescription Context triple: [Phineus, helpDescription, gave directions to Colchis]
-
A.
helpsIn
Indicates that one entity provides assistance, support, or aid to another entity in performing or achieving a particular task, activity, or goal.
-
B.
hasHelpPoint
Indicates that one entity provides or contains a designated help or assistance point for another entity.
-
C.
settingDescription
Indicates the descriptive details or characteristics that define the context or environment in which something occurs.
-
D.
usageInstruction
Indicates that one entity provides guidance or directions on how to properly use, operate, or handle another entity.
-
E.
outputDescription
Indicates that an entity produces or generates a particular description as its output.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26d34bc81908bb22087d434322d |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:37 p.m.