Triple
T16650031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Monadologie |
E404579
|
entity |
| Predicate | introducesDoctrine |
P41206
|
FINISHED |
| Object | pre-established harmony |
—
|
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: pre-established harmony | Statement: [La Monadologie, introducesDoctrine, pre-established harmony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesDoctrine Context triple: [La Monadologie, introducesDoctrine, pre-established harmony]
-
A.
developedDoctrine
Indicates that one entity created, formulated, or significantly advanced a particular doctrine or set of principles.
-
B.
sharesDoctrine
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
-
C.
teachesDoctrine
Indicates that one entity imparts, explains, or promotes a specific doctrine or set of beliefs to another entity.
-
D.
proposesDoctrine
chosen
Indicates that one entity formally puts forward or advocates a particular doctrine, theory, or set of principles for consideration or adoption by others.
-
E.
examinesDoctrine
Indicates that one entity critically studies, analyzes, or evaluates a particular doctrine or set of beliefs.
- 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_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. |
Created at: April 10, 2026, 5:18 a.m.