Triple
T34965906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Getty Tomb |
E1008395
|
entity |
| Predicate | hasCentralHonoree |
P75580
|
FINISHED |
| Object | Carrie Eliza Getty |
—
|
NE NERFINISHED |
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: Carrie Eliza Getty | Statement: [Getty Tomb, hasCentralHonoree, Carrie Eliza Getty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralHonoree Context triple: [Getty Tomb, hasCentralHonoree, Carrie Eliza Getty]
-
A.
hasNotableHonoree
Indicates that an entity is notably dedicated to, named after, or honors a particular person or group.
-
B.
honorsPerson
chosen
Indicates that one entity formally recognizes, respects, or pays tribute to a specific person.
-
C.
honoredPerson
Indicates that a person is the recipient of honor, recognition, or special distinction from another party or in a particular context.
-
D.
honoreeKnownFor
Indicates that an honoree is recognized or celebrated specifically for a particular work, achievement, contribution, or notable attribute.
-
E.
isPillarOf
Indicates that one entity serves as a fundamental support, foundation, or mainstay for another entity, often crucial to its stability, success, or existence.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4 p.m.