Triple
T3435920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epimenides paradox |
E72450
|
entity |
| Predicate | hasKeyStatement |
P41956
|
FINISHED |
| Object | All Cretans are liars |
—
|
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: All Cretans are liars | Statement: [Epimenides paradox, hasKeyStatement, All Cretans are liars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyStatement Context triple: [Epimenides paradox, hasKeyStatement, All Cretans are liars]
-
A.
hasKeyClaim
chosen
Indicates that one entity contains, presents, or is associated with a central or primary claim expressed by another entity.
-
B.
hasKeyDocument
Indicates that an entity possesses or is associated with a primary or essential document relevant to a particular context or process.
-
C.
hasKeyIssue
Indicates that an entity is associated with a primary or central problem, concern, or topic of importance.
-
D.
hasKeyElement
Indicates that one entity contains or depends on another entity that serves as a primary or essential component.
-
E.
hasKeyCapability
Indicates that an entity possesses an essential ability or function that is critical for performing a particular task or role.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9f2e4b4819085336fb539daf3c7 |
completed | March 8, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.