Triple
T4375129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GoRaleigh |
E98985
|
entity |
| Predicate | centralHubLocation |
P18768
|
FINISHED |
| Object | downtown Raleigh |
—
|
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: downtown Raleigh | Statement: [GoRaleigh, centralHubLocation, downtown Raleigh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralHubLocation Context triple: [GoRaleigh, centralHubLocation, downtown Raleigh]
-
A.
centralLocation
chosen
Indicates that one entity serves as the primary or central place associated with another entity.
-
B.
Global HubLocation
Indicates a location that serves as a central, primary hub for global operations, connections, or activities.
-
C.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
D.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an entity.
-
E.
secondaryHeadquartersLocation
Indicates the location where an organization maintains a secondary (non-primary) headquarters.
- 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352222df48190bead639e99635faf |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:18 p.m.