Triple
T9609566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Veragua |
E232062
|
entity |
| Predicate | originalGranteeRelation |
P168
|
FINISHED |
| Object | grandson of Christopher Columbus |
—
|
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: grandson of Christopher Columbus | Statement: [Duke of Veragua, originalGranteeRelation, grandson of Christopher Columbus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalGranteeRelation Context triple: [Duke of Veragua, originalGranteeRelation, grandson of Christopher Columbus]
-
A.
identityRelation
Indicates that two entities are in fact the very same entity, not merely similar or equivalent.
-
B.
originAssociatedWith
Indicates a relationship where an entity is connected to, derived from, or influenced by a particular origin, source, or point of beginning.
-
C.
grantedBy
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
-
D.
grantedTo
chosen
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
-
E.
originallyAssociatedWith
Indicates that an entity was first linked, connected, or affiliated with another entity before any later changes in association.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a8469e081909c8fb7c84ffea2b3 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.