Triple
T31303921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukedom of Cambridge |
E798281
|
entity |
| Predicate | grantedAlongWith |
P18476
|
FINISHED |
| Object | Earldom of Strathearn |
—
|
NE NERFINISHED |
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: Earldom of Strathearn | Statement: [Dukedom of Cambridge, grantedAlongWith, Earldom of Strathearn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedAlongWith Context triple: [Dukedom of Cambridge, grantedAlongWith, Earldom of Strathearn]
-
A.
grantedWith
chosen
Indicates that one entity is given, conferred, or endowed together with another entity as part of the same granting event or condition.
-
B.
grantedBy
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
-
C.
grantedIn
Indicates that something (such as a right, status, or permission) is formally conferred or authorized within a particular context, document, or jurisdiction.
-
D.
grantedTo
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
-
E.
grantedAs
Indicates that one entity is conferred, assigned, or bestowed in a particular role, status, or capacity to 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 29, 2026, 9:14 p.m.