Triple
T11665763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baroque scholasticism |
E277241
|
entity |
| Predicate | declinesBecauseOf |
P41905
|
FINISHED |
| Object | rise of Enlightenment philosophy |
—
|
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: rise of Enlightenment philosophy | Statement: [Baroque scholasticism, declinesBecauseOf, rise of Enlightenment philosophy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declinesBecauseOf Context triple: [Baroque scholasticism, declinesBecauseOf, rise of Enlightenment philosophy]
-
A.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
-
B.
declineTriggeredBy
chosen
Indicates that a decline event or state is caused or initiated by a specified triggering factor or condition.
-
C.
declinedDuring
Indicates that one entity’s value, condition, or status decreased over the course of a specified time period or event.
-
D.
declinedAround
Indicates that something decreased in value, intensity, or quantity in the time period surrounding a specified point or event.
-
E.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a43f438081909da476294a057c38 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.