Triple
T25370449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owen Sound Attack |
E632915
|
entity |
| Predicate | cityPopulationCategory |
P144473
|
FINISHED |
| Object | small market |
—
|
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: small market | Statement: [Owen Sound Attack, cityPopulationCategory, small market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityPopulationCategory Context triple: [Owen Sound Attack, cityPopulationCategory, small market]
-
A.
cityPopulationContext
Indicates the contextual relationship between a city and information about its population, such as size, distribution, or demographic characteristics.
-
B.
homeCityPopulationGroup
chosen
Indicates that an entity’s home city belongs to a specified population size category or range.
-
C.
countryPopulationContext
Indicates the contextual population characteristics or statistics associated with a specific country.
-
D.
populationFocus
Indicates that something is primarily directed toward, concerned with, or designed for a particular population or demographic group.
-
E.
homeCityPopulationRegion
Indicates that the population of a home city falls within or is associated with a specified geographic region.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4a11263048190aa4939dcd3572a49 |
completed | May 1, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:38 p.m.