Triple
T38459233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wells Fargo Plaza |
E912402
|
entity |
| Predicate | hasUndergroundTunnelConnection |
P41500
|
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: [Wells Fargo Plaza, hasUndergroundTunnelConnection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndergroundTunnelConnection Context triple: [Wells Fargo Plaza, hasUndergroundTunnelConnection, yes]
-
A.
hasUndergroundConnections
chosen
Indicates that one entity is linked to another through subterranean or hidden passageways, networks, or channels.
-
B.
hasSubwayOrUnderpass
Indicates that there exists a subway or underpass connecting or located at the related entities.
-
C.
hasUndergroundSection
Indicates that an entity includes a portion or segment that is located below ground level.
-
D.
hasRailwayTunnel
Indicates that one entity contains, includes, or is connected by a railway tunnel associated with the other entity.
-
E.
hasUndergroundLevel
Indicates that one entity possesses or includes a level, floor, or section that is located below ground level.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 3, 2026, 4:31 p.m.