Triple
T17538511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | matter (hyle) |
E427122
|
entity |
| Predicate | hasStatusInAristotle |
P15010
|
FINISHED |
| Object | one of four causes (material cause) |
—
|
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 four causes (material cause) | Statement: [matter (hyle), hasStatusInAristotle, one of four causes (material cause)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatusInAristotle Context triple: [matter (hyle), hasStatusInAristotle, one of four causes (material cause)]
-
A.
hasStatusIn
chosen
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
-
B.
hasStatusBasedOn
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
-
C.
statusInLogic
Indicates the logical status or role an entity holds within a formal reasoning or inference context.
-
D.
hasStatusLabel
Indicates that an entity is associated with a specific status expressed as a human-readable label.
-
E.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4536ec5f48190acff6671712d40c7 |
completed | April 19, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.