Triple
T20222793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrisonville High School |
E495298
|
entity |
| Predicate | hasServicePopulation |
P93194
|
FINISHED |
| Object | teenage students |
—
|
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: teenage students | Statement: [Harrisonville High School, hasServicePopulation, teenage students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServicePopulation Context triple: [Harrisonville High School, hasServicePopulation, teenage students]
-
A.
hasServiceAreaPopulation
Indicates that an entity has a service area characterized by a specific population size or count.
-
B.
servicePopulationType
chosen
Indicates the type or category of population that a service is intended to serve or target.
-
C.
hasPopulationStatus
Indicates the current demographic condition or classification of a population associated with an entity.
-
D.
hasCorePopulation
Indicates that an entity possesses a central or primary group of individuals that constitute its main population.
-
E.
hasIndicationPopulation
Indicates that a medical indication is specifically applicable to, or defined for, a particular population group.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd729548190942bcf842f03c4cd |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.