Triple
T27641660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip Stanhope (illegitimate son and letter recipient) |
E696601
|
entity |
| Predicate | correspondenceEndApprox |
P35259
|
FINISHED |
| Object | 1768 |
—
|
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: 1768 | Statement: [Philip Stanhope (illegitimate son and letter recipient), correspondenceEndApprox, 1768]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondenceEndApprox Context triple: [Philip Stanhope (illegitimate son and letter recipient), correspondenceEndApprox, 1768]
-
A.
corridorEndApprox
Indicates that one location is approximately at or near the end of a corridor relative to another location.
-
B.
officeEndApproximate
Indicates that an office or term ended around an approximate date rather than on a precisely known day.
-
C.
correspondsWith
Indicates that two entities are in mutual alignment or agreement, such that one matches, parallels, or is equivalent to the other in a specified respect.
-
D.
timePeriodEndApprox
chosen
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
E.
closerTo
Indicates that one entity is at a smaller distance to a reference entity than another entity is.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 2:26 p.m.