Triple
T24900140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embarcadero roadway |
E623551
|
entity |
| Predicate | hasFacilitiesFor |
P12416
|
FINISHED |
| Object | pedestrians |
—
|
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: pedestrians | Statement: [Embarcadero roadway, hasFacilitiesFor, pedestrians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFacilitiesFor Context triple: [Embarcadero roadway, hasFacilitiesFor, pedestrians]
-
A.
hasFacilities
chosen
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
B.
hasFacilityFunction
Indicates that a facility performs, supports, or is designated for a particular function or operational role.
-
C.
hasFacilityType
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
D.
hasFacilityLocation
Indicates that an entity possesses or is associated with a facility situated at a specific location.
-
E.
servesFacility
Indicates that one entity provides services or support to a particular facility as its client, target, or area of operation.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 5:27 a.m.