Triple
T16650027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Monadologie |
E404579
|
entity |
| Predicate | definesMonadsAs |
P124125
|
FINISHED |
| Object | simple substances without parts |
—
|
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: simple substances without parts | Statement: [La Monadologie, definesMonadsAs, simple substances without parts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesMonadsAs Context triple: [La Monadologie, definesMonadsAs, simple substances without parts]
-
A.
definesOperationsOf
Indicates that one entity specifies or determines the set, nature, or details of operations performed by another entity.
-
B.
definesLogicAs
Indicates that one entity specifies or establishes the logical rules, structure, or behavior to be used by another entity.
-
C.
numberOfMonks
Indicates the quantity or count of monks associated with a given entity or context.
-
D.
monasticCode
Indicates that an entity follows, is governed by, or is associated with a specific set of monastic rules or disciplinary code.
-
E.
definesSystemAs
Indicates that one entity explicitly specifies or establishes another entity as the system to be used, referenced, or treated as authoritative.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ad85ec881909dc6a434a363dab1 |
completed | April 18, 2026, 12:36 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:18 a.m.