Triple
T27435278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Monroe Street |
E690762
|
entity |
| Predicate | hasConnectingFacility |
P12416
|
FINISHED |
| Object | sidewalks |
—
|
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: sidewalks | Statement: [North Monroe Street, hasConnectingFacility, sidewalks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectingFacility Context triple: [North Monroe Street, hasConnectingFacility, sidewalks]
-
A.
hasTerminalFacility
Indicates that an entity possesses or includes a terminal facility used as an endpoint for transport, communication, or related operations.
-
B.
hasFacilityFunction
Indicates that a facility performs, supports, or is designated for a particular function or operational role.
-
C.
hasFacilities
chosen
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
D.
hasFacilityType
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
E.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
- 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: April 27, 2026, 12:43 p.m.