Triple
T1478769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Royal |
E30902
|
entity |
| Predicate | firstConferredApproximateYear |
P124
|
FINISHED |
| Object | 1642 |
—
|
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: 1642 | Statement: [Princess Royal, firstConferredApproximateYear, 1642]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstConferredApproximateYear Context triple: [Princess Royal, firstConferredApproximateYear, 1642]
-
A.
firstAwarded
chosen
Indicates the time or occasion when an award, honor, or recognition was given for the very first time.
-
B.
foundedAsUniversityIn
Indicates that an institution was originally established as a university in a specific year or time period.
-
C.
conferredOn
Indicates that something (such as an honor, title, degree, or benefit) has been formally granted or bestowed upon a particular entity.
-
D.
firstCelebratedInYear
Indicates the year in which something (such as an event, holiday, or celebration) was first observed or celebrated.
-
E.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c6739d2481909ea8d8e075f62cf3 |
completed | March 1, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69a4c484e52c81908948ff8c0a42751b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:11 p.m.