Triple
T13923555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renmin University of China area |
E334803
|
entity |
| Predicate | typicalPopulation |
P2750
|
FINISHED |
| Object | university 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: university students | Statement: [Renmin University of China area, typicalPopulation, university students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPopulation Context triple: [Renmin University of China area, typicalPopulation, university students]
-
A.
populationClass
Indicates a categorical classification of a population based on shared characteristics, status, or demographic criteria.
-
B.
populationIncludes
chosen
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
-
C.
peakPopulationApproximate
Indicates that the peak population of an entity is known only approximately rather than as an exact value.
-
D.
typicalCatchmentPopulation
Indicates the usual or expected number of people served by, or falling within the service area of, a given facility or resource.
-
E.
servicePopulationType
Indicates the type or category of population that a service is intended to serve or target.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa6cd9881908f652538f4613f37 |
completed | April 14, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.