Triple
T24321541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmony Chapel |
E612975
|
entity |
| Predicate | townPopulationContext |
P137370
|
FINISHED |
| Object | tiny town |
—
|
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: tiny town | Statement: [Harmony Chapel, townPopulationContext, tiny town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: townPopulationContext Context triple: [Harmony Chapel, townPopulationContext, tiny town]
-
A.
staffPopulationApprox
Indicates an approximate or estimated number of staff associated with an entity.
-
B.
populationTown
chosen
Indicates that a town has a specified number of inhabitants as its population.
-
C.
cityPopulationContext
Indicates the contextual relationship between a city and information about its population, such as size, distribution, or demographic characteristics.
-
D.
metroPopulationContext
Indicates that the population value is measured or interpreted specifically within the context of a metropolitan area (metro region) rather than another geographic or administrative unit.
-
E.
boroughPopulation
Indicates the total number of people living within a specific borough.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ac7fc08190993f707f2f97e7f5 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:51 a.m.