Triple
T29135170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phaedrus |
E738493
|
entity |
| Predicate | discussesMethod |
P51615
|
FINISHED |
| Object | collection and division (diairesis) |
—
|
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: collection and division (diairesis) | Statement: [Phaedrus, discussesMethod, collection and division (diairesis)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discussesMethod Context triple: [Phaedrus, discussesMethod, collection and division (diairesis)]
-
A.
disciplinaryMethod
Indicates a method or approach used to discipline, correct, or control another party’s behavior.
-
B.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
C.
methodologyType
Indicates the specific kind or category of method or procedure used in carrying out an activity or study.
-
D.
describesMethodology
chosen
Indicates that one entity explains, specifies, or characterizes the methodology or procedure used by another entity.
-
E.
interpretationMethod
Indicates the method, technique, or process used to interpret or derive meaning from something.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 11:33 a.m.