Triple
T28673780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keyhouse |
E725804
|
entity |
| Predicate | laterRenamedSetting |
P195226
|
FINISHED |
| Object | Matheson, Massachusetts |
—
|
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: Matheson, Massachusetts | Statement: [Keyhouse, laterRenamedSetting, Matheson, Massachusetts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRenamedSetting Context triple: [Keyhouse, laterRenamedSetting, Matheson, Massachusetts]
-
A.
laterDefinedSetting
Indicates that a particular setting is defined or specified at a later point in time relative to another reference or context.
-
B.
wasRenamedIn
Indicates that an entity changed its name to a different one at or during a specific time or event.
-
C.
wereRenamedAs
Indicates that one entity previously had a different name and was subsequently given or adopted the other entity as its new name.
-
D.
knownAsSettingFor
Indicates that something is recognized or regarded as the typical or notable setting or backdrop for something else.
-
E.
laterChangedNameTo
Indicates that an entity adopted a different name at a subsequent time, replacing its earlier name.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
| PDg | Predicate description generation | batch_69fdb3172b808190b590d7c5be31ebb7 |
completed | May 8, 2026, 9:55 a.m. |
Created at: April 28, 2026, 5:05 a.m.