Triple
T31622833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larry Aldrich Museum |
E806939
|
entity |
| Predicate | hasRenamedStatus |
P203451
|
FINISHED |
| Object | defunct under original name |
—
|
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: defunct under original name | Statement: [Larry Aldrich Museum, hasRenamedStatus, defunct under original name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRenamedStatus Context triple: [Larry Aldrich Museum, hasRenamedStatus, defunct under original name]
-
A.
renamedTo
Indicates that an entity has been given a new name, specifying the target name it was changed to.
-
B.
hasNameBeforeChange
Indicates that an entity is associated with the name it had prior to some change or renaming event.
-
C.
canBeRenamedTo
Indicates that one entity is allowed or able to have its name changed to match another specified name or identifier.
-
D.
wasRenamedIn
Indicates that an entity changed its name to a different one at or during a specific time or event.
-
E.
renamedInPeriod
Indicates that an entity underwent a renaming during a specified time period.
- F. None of above. chosen
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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01839b071481909f9cc79a6a09387d |
completed | May 11, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_6a017edbed688190baa61cbae5110c8e |
completed | May 11, 2026, 7:01 a.m. |
| PDg | Predicate description generation | batch_6a01839a63a48190a59a6c4464db0eea |
completed | May 11, 2026, 7:22 a.m. |
Created at: April 30, 2026, 10:42 p.m.