Triple
T16130768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol/Rice Street Station |
E391388
|
entity |
| Predicate | hasWayfindingMaps |
P51898
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Capitol/Rice Street Station, hasWayfindingMaps, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWayfindingMaps Context triple: [Capitol/Rice Street Station, hasWayfindingMaps, yes]
-
A.
hasTouristSignage
chosen
Indicates that there is official signage present to guide or inform tourists about a place, route, or attraction.
-
B.
mapsIncluded
Indicates that one map or mapping is contained within, or is a subset of, another map or mapping.
-
C.
canProvideDirections
Indicates that one entity is able to give another entity guidance or instructions on how to reach a particular location or navigate a route.
-
D.
mapsFrom
Indicates that one entity is derived, transformed, or constructed based on data, structure, or content originating from another entity.
-
E.
mapsDepict
Indicates that maps visually represent or illustrate the geographic features, locations, or spatial relationships of something.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2020829e88190b51ab32d22cf0259 |
completed | April 17, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.