Triple
T4712843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astoria–Ditmars Boulevard |
E104556
|
entity |
| Predicate | terminalRole |
P5518
|
FINISHED |
| Object | northern terminal of the BMT Astoria Line |
—
|
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: northern terminal of the BMT Astoria Line | Statement: [Astoria–Ditmars Boulevard, terminalRole, northern terminal of the BMT Astoria Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalRole Context triple: [Astoria–Ditmars Boulevard, terminalRole, northern terminal of the BMT Astoria Line]
-
A.
remoteTerminalRole
Indicates that an entity has a specific role or permission level when accessing or operating a system through a remote terminal.
-
B.
terminalName
Indicates the name or label assigned to a specific terminal or endpoint within a system or network.
-
C.
terminal
Indicates that one entity is the final or end point in a process, sequence, or structure, beyond which no further continuation occurs.
-
D.
typeOfRole
chosen
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
E.
displayRole
Indicates the role or position an entity holds in the context of how it is presented or shown in a display.
- 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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.