Triple
T8768772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summit City |
E208402
|
entity |
| Predicate | isPopularNameIn |
P22212
|
FINISHED |
| Object | northeastern Indiana |
—
|
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: northeastern Indiana | Statement: [Summit City, isPopularNameIn, northeastern Indiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopularNameIn Context triple: [Summit City, isPopularNameIn, northeastern Indiana]
-
A.
isCommonAsFirstName
Indicates that the referenced name is frequently used as a first (given) name within a specified population or context.
-
B.
isAmongMostCommonSurnamesIn
Indicates that a surname ranks within the group of most frequently occurring surnames in a specified region or population.
-
C.
isPopularWith
Indicates that one entity is well-liked, favored, or widely accepted by another entity or group.
-
D.
popularName
chosen
Indicates that the object is a commonly used or widely recognized name or nickname for the subject.
-
E.
namePopularityType
Indicates the category or type of popularity associated with a given name (e.g., how or in what way the name is considered popular).
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5eec49708190ba760d81a7974c50 |
completed | March 31, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:41 p.m.