Triple
T17967650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Disappointment |
E449254
|
entity |
| Predicate | ledToDoctrine |
P97539
|
FINISHED |
| Object | investigative judgment |
—
|
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: investigative judgment | Statement: [Great Disappointment, ledToDoctrine, investigative judgment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledToDoctrine Context triple: [Great Disappointment, ledToDoctrine, investigative judgment]
-
A.
createdDoctrine
Indicates that an entity originated, formulated, or established a particular doctrine, theory, or set of principles.
-
B.
sharesDoctrine
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
-
C.
usesDoctrine
Indicates that one entity applies, follows, or relies on a particular doctrine in its actions or reasoning.
-
D.
definedDoctrineAt
Indicates that a particular doctrine was formally established, articulated, or codified at a specific place or time.
-
E.
contributesToDoctrine
chosen
Indicates that one entity plays a role in forming, shaping, or supporting the doctrinal position or belief system of another entity.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b13935908190b5269a84a3df2460 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.