Triple
T22675363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rule of reason |
E560329
|
entity |
| Predicate | furtherDevelopedInCaseYear |
P121968
|
FINISHED |
| Object | 1918 |
—
|
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: 1918 | Statement: [rule of reason, furtherDevelopedInCaseYear, 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: furtherDevelopedInCaseYear Context triple: [rule of reason, furtherDevelopedInCaseYear, 1918]
-
A.
developedInCase
Indicates that something (such as a method, argument, or principle) was formulated, articulated, or established within the context of a particular case.
-
B.
yearOfDevelopment
Indicates the specific year in which something was developed or created.
-
C.
notableCaseYear
Indicates the year in which a particular case became notable or gained recognized significance.
-
D.
investigationYear
Indicates the specific calendar year in which an investigation takes place or is formally conducted.
-
E.
elaboratedInYear
chosen
Indicates that something was further developed, detailed, or expanded upon in a specific calendar year.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17823bd1881908958b0a8ba59e199 |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:11 p.m.