Triple
T32745955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charleston metropolitan area |
E837353
|
entity |
| Predicate | isStateCapitalMetro |
P176988
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Charleston metropolitan area, isStateCapitalMetro, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStateCapitalMetro Context triple: [Charleston metropolitan area, isStateCapitalMetro, true]
-
A.
isMetropolitanFor
Indicates that one entity serves as the primary metropolitan center or urban hub for another entity (such as a region, area, or service).
-
B.
hasMetropolitanCityCapital
Indicates that an administrative region or entity has, as its capital, a city classified as a metropolitan city.
-
C.
isStateCapital
Indicates that a city serves as the official capital of a given state.
-
D.
isMetropolitanOf
Indicates that one entity is the primary metropolitan area or major urban center associated with another entity, such as a region, country, or administrative division.
-
E.
isCity
Indicates that the subject entity is classified as a city.
- F. None of above. chosen
Provenance (4 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f814fcf48190ae4504154d1b2c05 |
completed | May 3, 2026, 7:24 a.m. |
Created at: May 1, 2026, 1:12 a.m.