Triple
T27286851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randy Turpin |
E688499
|
entity |
| Predicate | rematchLocation |
P162307
|
FINISHED |
| Object | Polo Grounds, New York City |
—
|
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: Polo Grounds, New York City | Statement: [Randy Turpin, rematchLocation, Polo Grounds, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rematchLocation Context triple: [Randy Turpin, rematchLocation, Polo Grounds, New York City]
-
A.
reopenedInCurrentLocation
Indicates that an entity, after having been closed or moved, has been opened again at its present location.
-
B.
repeatLocation
Indicates that an entity occurs or appears multiple times at the same location or position.
-
C.
reentryLocation
Indicates the place or area where an entity returns or re-enters after having left or exited a previous location or state.
-
D.
remainsLocation
Indicates that the physical remains of an entity are located or kept at a specified place.
-
E.
previousLocationReplaced
Indicates that one location has been superseded or taken over by another location, replacing its previous role or position.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f627565c688190a8f4f9fd9ce84990 |
completed | May 2, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 11:12 a.m.