Triple
T30094483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A New Brain |
E764824
|
entity |
| Predicate | revivalLocation |
P23817
|
FINISHED |
| Object | New York City Center |
—
|
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: New York City Center | Statement: [A New Brain, revivalLocation, New York City Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalLocation Context triple: [A New Brain, revivalLocation, New York City Center]
-
A.
notableRevivalLocation
chosen
Indicates that a place is recognized as a significant site where something (such as a work, practice, or tradition) was revived or brought back into prominence.
-
B.
resurrectionPlace
Indicates the location where an entity is brought back to life or restored from death.
-
C.
revivalCenter
Indicates that an entity serves as a central place or hub where revival, restoration, or renewal activities for another entity occur.
-
D.
rescuedLocation
Indicates the place where a rescue action occurred or from which someone or something was rescued.
-
E.
revelationPlace
Indicates the place or location where a revelation, disclosure, or revealing event occurs.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d8f52e88190b3a11f62835ea328 |
completed | May 2, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:07 p.m.