Triple
T19901911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sixth Labour of Heracles |
E478311
|
entity |
| Predicate | hasResultForHeracles |
P137757
|
FINISHED |
| Object | completion of sixth labour |
—
|
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: completion of sixth labour | Statement: [sixth Labour of Heracles, hasResultForHeracles, completion of sixth labour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResultForHeracles Context triple: [sixth Labour of Heracles, hasResultForHeracles, completion of sixth labour]
-
A.
hasMainResult
Indicates that one entity is the primary or most significant outcome, conclusion, or result produced by another entity or process.
-
B.
hasKeyResult
Indicates that an entity is associated with a specific key result it aims to achieve or is responsible for.
-
C.
hasClassicResult
Indicates that an entity is associated with a canonical, established, or traditionally recognized result or outcome.
-
D.
searchesResultedIn
Indicates that a search action produced or led to specific results.
-
E.
hasConclusion
Indicates that something leads to, results in, or is associated with a particular conclusion.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65943aefc81909e873e1845d5af3d |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:52 p.m.