Triple
T1685683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laws |
E36435
|
entity |
| Predicate | positionInPlatosWorks |
P19302
|
FINISHED |
| Object | one of Plato’s last dialogues |
—
|
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: one of Plato’s last dialogues | Statement: [Laws, positionInPlatosWorks, one of Plato’s last dialogues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInPlatosWorks Context triple: [Laws, positionInPlatosWorks, one of Plato’s last dialogues]
-
A.
positionInAuthorOeuvre
chosen
Indicates the relative placement or order of a work within an author's overall body of work.
-
B.
positionInPantheon
Indicates the rank, role, or hierarchical standing that a deity or figure holds within a specific pantheon or religious hierarchy.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
-
E.
positionInMass
Indicates that an entity occupies a specific location or role within a larger undifferentiated group, collection, or mass.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.