Triple
T34093256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tryon Street |
E874352
|
entity |
| Predicate | hasCentrality |
P4408
|
FINISHED |
| Object | one of Charlotte’s main streets |
—
|
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: one of Charlotte’s main streets | Statement: [Tryon Street, hasCentrality, one of Charlotte’s main streets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentrality Context triple: [Tryon Street, hasCentrality, one of Charlotte’s main streets]
-
A.
isCentralTo
chosen
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
B.
hasCentralDensity
Indicates that an entity possesses a specified value for its density at the central or core region.
-
C.
hasCentralIntensity
Indicates that something possesses a specific value or measure of intensity at its central point or core region.
-
D.
hasBarycenter
Indicates that one entity serves as the barycenter (center of mass) of another entity or system.
-
E.
hasCenterIn
Indicates that something is located, based, or primarily focused within a specified central place or area.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 1, 2026, 1:52 a.m.