Triple
T7152855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livonia Avenue (BMT Canarsie Line) via Junius Street transfer |
E166733
|
entity |
| Predicate | transferVia |
P39909
|
FINISHED |
| Object | street level |
—
|
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: street level | Statement: [Livonia Avenue (BMT Canarsie Line) via Junius Street transfer, transferVia, street level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferVia Context triple: [Livonia Avenue (BMT Canarsie Line) via Junius Street transfer, transferVia, street level]
-
A.
transferType
Indicates the specific method or category of how something is transferred from one entity to another.
-
B.
transferAfter
Indicates that one entity transfers something to another entity only after a specified event or condition has occurred.
-
C.
transferMode
chosen
Indicates the method or mechanism by which something is transferred from one entity to another.
-
D.
transferEvent
Indicates an event in which something is moved, handed over, or reassigned from one entity to another.
-
E.
transferDestination
Indicates the entity that serves as the receiving end or target location of a transfer from another entity.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f52c1081908c4fa424d5e965bc |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.