Triple
T6734751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Althorp |
E153724
|
entity |
| Predicate | traditionalHolderRole |
P39110
|
FINISHED |
| Object | eldest son of the Earl Spencer |
—
|
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: eldest son of the Earl Spencer | Statement: [Viscount Althorp, traditionalHolderRole, eldest son of the Earl Spencer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalHolderRole Context triple: [Viscount Althorp, traditionalHolderRole, eldest son of the Earl Spencer]
-
A.
traditionalTitleHolder
chosen
Indicates that one entity holds a customary or historically established title or rank in relation to another entity.
-
B.
notableHolderRole
Indicates that an entity is recognized for holding a particular role, office, or position in a notable or distinguished capacity.
-
C.
originalHolder
Indicates that an entity is the initial possessor or owner of another entity before any transfer, change, or reassignment occurs.
-
D.
traditionalLeader
Indicates that an entity holds a customary or historically established leadership role within a community or group.
-
E.
ownerRole
Indicates the role or capacity in which an entity serves as the owner of 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_69c6880bdd68819097de8b6099992682 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16ecbe08190b019d547f631a725 |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:09 p.m.