Triple
T28920163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Route Ferguson |
E733485
|
entity |
| Predicate | notableBuildingOnStreet |
P203630
|
FINISHED |
| Object | Wukang Mansion |
E188537
|
NE 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: Wukang Mansion | Statement: [Route Ferguson, notableBuildingOnStreet, Wukang Mansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBuildingOnStreet Context triple: [Route Ferguson, notableBuildingOnStreet, Wukang Mansion]
-
A.
isThoroughfareFor
Indicates that something serves as a route or passageway used for travel or transportation between places.
-
B.
hasHeadquartersOnStreet
Indicates that an organization’s headquarters is located on a specific street.
-
C.
avenueRadiatingFrom
Indicates that one avenue extends outward from and is oriented away from another central point or thoroughfare, like a spoke radiating from a hub.
-
D.
hasNotableStreet
Indicates that an entity is associated with a particular street that is considered notable or significant.
-
E.
hasBuildingUseAlongStreet
Indicates that a building located along a particular street is used for a specified purpose or function in relation to that street.
- F. None of above. chosen
Provenance (5 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a01b935e3948190a7af37b07938d618 |
completed | May 11, 2026, 11:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24d41d69188190a3a8b43a6649662d |
completed | June 7, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_6a01b8d198b48190b01e16ac9ce7e7bd |
completed | May 11, 2026, 11:09 a.m. |
| PDg | Predicate description generation | batch_6a01b9353e4c8190991c80e7c01a015b |
completed | May 11, 2026, 11:10 a.m. |
Created at: April 28, 2026, 8:19 a.m.