Triple
T17313944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organon model of language |
E420371
|
entity |
| Predicate | relatesElement |
P84787
|
FINISHED |
| Object | speaker |
—
|
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: speaker | Statement: [Organon model of language, relatesElement, speaker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatesElement Context triple: [Organon model of language, relatesElement, speaker]
-
A.
elementalAssociation
Indicates an association where one entity is linked or related to a particular element or elemental property (such as fire, water, earth, or air).
-
B.
relatesComplementTo
Indicates that one entity serves as a complement or completing counterpart to another entity within a specified context or structure.
-
C.
subjectRelation
chosen
Indicates that one entity stands in a specified relational role or connection to another entity.
-
D.
associatedWithElement
Indicates a relationship where one entity is linked or connected to a particular element, such that the element is relevant to, involved in, or characteristic of that entity.
-
E.
relatedShowElement
Indicates that one show element is associated with or connected to another show element in some relevant way.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399b4dcc8190996d79d04ba88795 |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.