Triple
T23386079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theseus and Cercyon |
E593883
|
entity |
| Predicate | demonstratesQualityOf |
P202
|
FINISHED |
| Object | Theseus’s physical strength |
—
|
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: Theseus’s physical strength | Statement: [Theseus and Cercyon, demonstratesQualityOf, Theseus’s physical strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demonstratesQualityOf Context triple: [Theseus and Cercyon, demonstratesQualityOf, Theseus’s physical strength]
-
A.
demonstratedBy
chosen
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
-
B.
supportsQuality
Indicates that one entity contributes to maintaining, enhancing, or ensuring the quality or standard of another entity or process.
-
C.
demonstratesTo
Indicates that one entity actively shows, explains, or proves something to another entity.
-
D.
recognisedQuality
Indicates that one entity acknowledges, identifies, or validates a particular quality or attribute present in another entity.
-
E.
demonstratedAgainst
Indicates that one party publicly protested or showed opposition toward another party or issue.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a498286c8190abfa381649812cf0 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:35 p.m.