Triple
T1685983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form of the Good |
E36441
|
entity |
| Predicate | functionInAnalogy |
P23285
|
FINISHED |
| Object | illuminates intelligible objects |
—
|
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: illuminates intelligible objects | Statement: [Form of the Good, functionInAnalogy, illuminates intelligible objects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInAnalogy Context triple: [Form of the Good, functionInAnalogy, illuminates intelligible objects]
-
A.
functionHypothesis
Indicates that an entity is proposed or assumed to serve as a function or functional explanation for another entity or phenomenon.
-
B.
intendedFunction
Indicates that something is designed or purposed to perform a particular role, use, or function.
-
C.
associatedFunction
chosen
Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
-
D.
notFunction
Indicates that the specified entity does not serve as a function or is not used in a functional role within the given context.
-
E.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
- 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.