Triple
T24786847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 89 East 42nd Street |
E620140
|
entity |
| Predicate | isMajorEntranceFor |
P26211
|
FINISHED |
| Object | Grand Central Terminal |
—
|
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: Grand Central Terminal | Statement: [89 East 42nd Street, isMajorEntranceFor, Grand Central Terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorEntranceFor Context triple: [89 East 42nd Street, isMajorEntranceFor, Grand Central Terminal]
-
A.
isMainEntrance
Indicates that an entrance serves as the primary or principal access point to a place or building.
-
B.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
C.
isMajorAccessPointFor
chosen
Indicates that something serves as a primary or significant entry or connection point for accessing another entity or system.
-
D.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
E.
hasLandmarkAtEntrance
Indicates that a specific landmark is located at or directly adjacent to the entrance of something.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 4:46 a.m.