Triple
T18812020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard II, Duke of Normandy |
E460036
|
entity |
| Predicate | relationToWilliamTheConqueror |
P57937
|
FINISHED |
| Object | grandfather |
—
|
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: grandfather | Statement: [Richard II, Duke of Normandy, relationToWilliamTheConqueror, grandfather]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToWilliamTheConqueror Context triple: [Richard II, Duke of Normandy, relationToWilliamTheConqueror, grandfather]
-
A.
relationTypeToHenryVIII
Indicates the specific type of relationship an entity has to Henry VIII (e.g., familial, political, or social connection).
-
B.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
-
C.
associatedNobleFamily
Indicates a relationship where an entity is linked or connected to a particular noble family, typically by heritage, allegiance, or formal association.
-
D.
predecessorAsDukeOfNormandy
Indicates that one entity previously held the title of Duke of Normandy immediately before another entity.
-
E.
hasRoyalAncestryFrom
chosen
Indicates that one entity possesses royal lineage or descent originating from 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3dcc7d88190801d9c9202e0e411 |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.