Triple
T29214916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meditatio quinta |
E740639
|
entity |
| Predicate | hasKeyArgumentType |
P176738
|
FINISHED |
| Object | a priori argument |
—
|
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: a priori argument | Statement: [Meditatio quinta, hasKeyArgumentType, a priori argument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyArgumentType Context triple: [Meditatio quinta, hasKeyArgumentType, a priori argument]
-
A.
hasArgumentType
Indicates that an argument or parameter in a function, method, or relation is of a specified data type or class.
-
B.
hasArgument
Indicates that one entity serves as an argument (such as an input, parameter, or participant) in relation to another entity, typically a function, event, or statement.
-
C.
hasParameterType
Indicates that a parameter in a function, method, or operation is associated with a specific data type.
-
D.
hasKeyType
Indicates that an entity possesses or is associated with a specific category or type of key.
-
E.
hasKeyFunction
Indicates that one entity serves as a primary or essential function or role for another entity.
- F. None of above. chosen
Provenance (4 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 28, 2026, 12:13 p.m.