Triple
T1684848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 7th Avenue (53rd Street Line) |
E36418
|
entity |
| Predicate | wifiAvailable |
P32735
|
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: [7th Avenue (53rd Street Line), wifiAvailable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wifiAvailable Context triple: [7th Avenue (53rd Street Line), wifiAvailable, yes]
-
A.
supportsWiFiStandard
Indicates that one entity is compatible with and able to operate using a specified Wi-Fi communication standard defined by another entity.
-
B.
networkCoverage
Indicates the extent to which a network’s signal or service is available across a given area or to specific entities.
-
C.
isOnLine
Indicates that one entity is located directly along, or in contact with, a specified line or linear path.
-
D.
offersInFlightWiFi
Indicates that an entity provides wireless internet access to passengers during a flight.
-
E.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aba644070c81908745b56d981fe273 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61b57a6881909373af287ef24799 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aba641e6a881909645577e72b53df2 |
completed | March 7, 2026, 4:14 a.m. |
Created at: March 4, 2026, 7:29 p.m.