Triple
T11055078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luther v. Borden |
E261352
|
entity |
| Predicate | contributesToDoctrine |
P97539
|
FINISHED |
| Object | separation of powers |
—
|
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: separation of powers | Statement: [Luther v. Borden, contributesToDoctrine, separation of powers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contributesToDoctrine Context triple: [Luther v. Borden, contributesToDoctrine, separation of powers]
-
A.
usesDoctrine
Indicates that one entity applies, follows, or relies on a particular doctrine in its actions or reasoning.
-
B.
containsDoctrine
Indicates that one entity includes, embodies, or incorporates the doctrine, principles, or teachings represented by another entity.
-
C.
definedDoctrineAt
Indicates that a particular doctrine was formally established, articulated, or codified at a specific place or time.
-
D.
sharesDoctrine
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
-
E.
replacedByDoctrine
Indicates that one doctrine has been superseded and taken its place by another doctrine.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798a0890481909c1d4f9d5b23f33a |
completed | April 9, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.