Triple
T3151924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fifth Avenue–53rd Street |
E65895
|
entity |
| Predicate | hasCellService |
P46630
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fifth Avenue–53rd Street, hasCellService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCellService Context triple: [Fifth Avenue–53rd Street, hasCellService, yes]
-
A.
hasTelephoneService
Indicates that a subject is provided with or connected to telephone service.
-
B.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
C.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
D.
hasBroadcastService
Indicates that an entity provides or is associated with a particular broadcast service.
-
E.
hasServiceCenter
Indicates that an entity maintains or is associated with a service center that provides support, repair, or maintenance services.
- 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_69ad8584485081909ed529e890cadc4a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5c27258819099c46a657779780b |
completed | March 8, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfbf0348190952a6bca8fc5fed1 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada1e4f7288190a80a1672e458132d |
completed | March 8, 2026, 4:20 p.m. |
Created at: March 8, 2026, 3:05 p.m.