Triple
T27089063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harper Avery Award |
E686110
|
entity |
| Predicate | renamedInUniverseReason |
P2136
|
FINISHED |
| Object | scandal involving Harper Avery and the foundation |
—
|
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: scandal involving Harper Avery and the foundation | Statement: [Harper Avery Award, renamedInUniverseReason, scandal involving Harper Avery and the foundation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamedInUniverseReason Context triple: [Harper Avery Award, renamedInUniverseReason, scandal involving Harper Avery and the foundation]
-
A.
nameChangeReason
chosen
Indicates the reason or justification for a change in an entity’s name.
-
B.
adoptedNewNameDueTo
Indicates that an entity changed its original name to a new one as a result of, or in response to, another specified entity or circumstance.
-
C.
realmRenamedFrom
Indicates that a realm currently known by one name previously had a different name from which it was renamed.
-
D.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
E.
formedByRenaming
Indicates that one entity is created or derived from another entity specifically through a change of name.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623480110819088369af135123c24 |
completed | May 2, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:39 a.m.