Triple
T34993174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl Nelson |
E1009448
|
entity |
| Predicate | associatedForeignTitle |
P46701
|
FINISHED |
| Object | Duca di Bronte |
E283408
|
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: Duca di Bronte | Statement: [Earl Nelson, associatedForeignTitle, Duca di Bronte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedForeignTitle Context triple: [Earl Nelson, associatedForeignTitle, Duca di Bronte]
-
A.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
B.
associatedTitleType
Indicates the type or category of a title that is linked or related to another entity or primary title.
-
C.
associatedTitleLocation
Indicates a relationship where a title is linked to a specific location with which it is contextually or formally connected.
-
D.
relatedTitleHolder
Indicates that one entity holds a title or position that is related or connected to the title or position held by another entity.
-
E.
equivalentOrRelatedTitle
chosen
Indicates that two titles are the same or sufficiently similar in meaning, role, or status to be treated as equivalent or closely related.
- 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.