Triple
T37801257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Stoa |
E942380
|
entity |
| Predicate | logicalDoctrine |
P47418
|
FINISHED |
| Object | lekta (sayables) |
—
|
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: lekta (sayables) | Statement: [Early Stoa, logicalDoctrine, lekta (sayables)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logicalDoctrine Context triple: [Early Stoa, logicalDoctrine, lekta (sayables)]
-
A.
codifiedDoctrine
Indicates that a set of beliefs, principles, or rules has been formally systematized and recorded as an official doctrine.
-
B.
doctrineOf
chosen
Indicates a relationship where one entity is the doctrinal teaching, principle, or belief system associated with, derived from, or formally held by another entity.
-
C.
confirmedDoctrine
Indicates that an authority has officially validated, endorsed, or ratified a particular doctrine as true or acceptable.
-
D.
alternativeDoctrine
Indicates that one doctrine serves as an alternative or substitute to another doctrine within a given context.
-
E.
developedDoctrine
Indicates that one entity created, formulated, or significantly advanced a particular doctrine or set of principles.
- 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_69f76ee6f1f4819091e2cf9c9e6aee19 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.