Triple
T28736777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tri-Cities |
E730821
|
entity |
| Predicate | hasNumberOfCoreMunicipalities |
P30910
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Tri-Cities, hasNumberOfCoreMunicipalities, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfCoreMunicipalities Context triple: [Tri-Cities, hasNumberOfCoreMunicipalities, 3]
-
A.
hasNumberOfMunicipalities
chosen
Indicates the relationship that specifies how many municipalities are associated with or contained within a given administrative or geographic entity.
-
B.
hasCoreTown
Indicates that an entity possesses or is associated with a primary or central town that serves as its main urban center.
-
C.
hasNumberOfAdministrativeTerritorialEntities
Indicates the count of administrative territorial units (such as states, provinces, or districts) that an entity is divided into or comprises.
-
D.
hasNumberOfComponentCities
Indicates the relationship that specifies how many component cities are contained within or associated with a given entity.
-
E.
isCoreCity
Indicates that a city serves as a primary, central, or most important urban area within a larger region, system, or network.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:01 a.m.