Triple
T13139485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queens Botanical Garden |
E312173
|
entity |
| Predicate | reestablishedAtCurrentSite |
P40520
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Queens Botanical Garden, reestablishedAtCurrentSite, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reestablishedAtCurrentSite Context triple: [Queens Botanical Garden, reestablishedAtCurrentSite, 1960s]
-
A.
relocatedToCurrentSite
Indicates that an entity moved from its previous location to the place where it is currently situated.
-
B.
reopenedOnSiteOf
Indicates that something has been reopened at the same physical location where it previously existed or operated.
-
C.
re-establishedAfter
Indicates that a relationship or state was previously ended or inactive and then brought back into effect following a specified event or time.
-
D.
reestablishedUnderCurrentName
Indicates that an entity previously existed under a different name and was later reestablished using its current name.
-
E.
reopenedInCurrentLocation
chosen
Indicates that an entity, after having been closed or moved, has been opened again at its present location.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b6a4348190b9922ed255759078 |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:09 p.m.