Triple
T30771626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Avenue subway corridor |
E783538
|
entity |
| Predicate | followsUnder |
P193546
|
FINISHED |
| Object | Fourth Avenue |
—
|
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: Fourth Avenue | Statement: [Fourth Avenue subway corridor, followsUnder, Fourth Avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsUnder Context triple: [Fourth Avenue subway corridor, followsUnder, Fourth Avenue]
-
A.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
B.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
-
C.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
-
D.
followedIn
Indicates that one entity began following or subscribing to another entity, typically in a social or sequential context.
-
E.
followsDisc
Indicates that one entity comes after another in a sequence or order, typically in a discrete or stepwise progression.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69fd49f612a4819096fe7d5a3bb439ba |
completed | May 8, 2026, 2:27 a.m. |
Created at: April 29, 2026, 8:40 p.m.