Triple
T34993184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl Nelson |
E1009448
|
entity |
| Predicate | associatedPersonRank |
P11700
|
FINISHED |
| Object | Vice-Admiral of the White |
E755171
|
NE 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: Vice-Admiral of the White | Statement: [Earl Nelson, associatedPersonRank, Vice-Admiral of the White]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPersonRank Context triple: [Earl Nelson, associatedPersonRank, Vice-Admiral of the White]
-
A.
associatedWithRank
chosen
Indicates a relationship where an entity is linked to a specific rank, level, or hierarchical position.
-
B.
associatedPersonField
Indicates that there is a person linked or connected to the subject in a relevant or contextual way.
-
C.
associatedPersonNotability
Indicates that the relationship specifies the notable characteristic, achievement, or reason for prominence of the associated person.
-
D.
associatedPeopleStatus
Indicates the role, condition, or standing of people who are connected or linked to a given entity or event.
-
E.
namedPersonAssociation
Indicates a relationship where one entity is associated with or identified by a specific personal name.
- F. None of above.
Provenance (4 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37b28b75e48190848542bd083179d8 |
completed | June 21, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.