Triple
T16237275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fruitlands Museum |
E394146
|
entity |
| Predicate | operatorChangeDate |
P92815
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Fruitlands Museum, operatorChangeDate, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorChangeDate Context triple: [Fruitlands Museum, operatorChangeDate, 2016]
-
A.
platformChangeDate
Indicates the date on which a platform undergoes or records a change, such as an update, migration, or modification.
-
B.
administrativeChangeDate
chosen
Indicates the date on which an administrative change (such as an update, modification, or reclassification) affecting the entity was officially recorded or took effect.
-
C.
dateChangesWith
Indicates that the date associated with one entity is altered or updated in conjunction with, or as a result of, a change involving another entity.
-
D.
startDateChangedTo
Indicates that the start date of something has been modified from its previous value to a new specified date.
-
E.
nameChangeDate
Indicates the date on which an entity’s name was officially changed.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2455bb23881909c4cb4c1439d2bc5 |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.