Triple
T448803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phaedo |
E7081
|
entity |
| Predicate | containsArgument |
P11236
|
FINISHED |
| Object | argument from opposites |
—
|
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: argument from opposites | Statement: [Phaedo, containsArgument, argument from opposites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsArgument Context triple: [Phaedo, containsArgument, argument from opposites]
-
A.
hasParameter
Indicates that an entity is associated with a specific parameter that defines or constrains some aspect of its behavior, configuration, or characteristics.
-
B.
includesElement
chosen
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
C.
containsCharacter
Indicates that one entity includes a specific character as part of its content or composition.
-
D.
hasTerm
Indicates that an entity includes, is associated with, or is defined by a specific term or condition.
-
E.
argumentType
Indicates that one entity serves as a specific semantic or syntactic argument role (such as subject, object, or complement) in relation to another entity or event.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef6755a08190a057e72279b70456 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2ede1a1108190a4a06b3416ae6156 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.