Triple
T17538500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | matter (hyle) |
E427122
|
entity |
| Predicate | isExplainedUsing |
P3638
|
FINISHED |
| Object | potentiality–actuality distinction |
—
|
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: potentiality–actuality distinction | Statement: [matter (hyle), isExplainedUsing, potentiality–actuality distinction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExplainedUsing Context triple: [matter (hyle), isExplainedUsing, potentiality–actuality distinction]
-
A.
usedToExplain
chosen
Indicates that one entity serves as an explanation or clarification for another entity.
-
B.
hasOfficialExplanation
Indicates that an entity is accompanied by an authoritative or formally recognized explanation clarifying its reason, cause, or details.
-
C.
isUsedToIllustrate
Indicates that one entity serves as an example or demonstration to clarify, explain, or represent another entity.
-
D.
hasInitialExplanation
Indicates that an entity is associated with an original or first explanation provided at the beginning of a process, interaction, or presentation.
-
E.
laterExplained
Indicates that an earlier event, statement, or situation is clarified or made understandable by information provided at a subsequent time.
- 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_69e4536dbe908190ba7559f9561f05a2 |
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.