Triple
T34950367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grant Road area |
E1007974
|
entity |
| Predicate | hasNearbyHub |
P200345
|
FINISHED |
| Object | Marine Lines |
—
|
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: Marine Lines | Statement: [Grant Road area, hasNearbyHub, Marine Lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHub Context triple: [Grant Road area, hasNearbyHub, Marine Lines]
-
A.
hasNearbyFacility
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
B.
hasNeighborhoodHub
chosen
Indicates that one place serves as a central local hub or focal point for community activities within a particular neighborhood.
-
C.
hasNearbyBay
Indicates that one entity is located close to or adjacent to a bay associated with the other entity.
-
D.
hasNearbyBase
Indicates that one entity has a base or facility located in close physical proximity to another entity or location.
-
E.
hasOutletNear
Indicates that one entity has a physical outlet or branch located in close proximity to another specified location or 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fff09dae088190bd8460060d778feb |
completed | May 10, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69fff0027c5c8190baa5c7a15852cbe0 |
completed | May 10, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4 p.m.