Triple
T28075875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langya Commandery |
E709539
|
entity |
| Predicate | populationRecordedIn |
P158141
|
FINISHED |
| Object | Book of Han |
—
|
NE NERFINISHED |
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: Book of Han | Statement: [Langya Commandery, populationRecordedIn, Book of Han]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationRecordedIn Context triple: [Langya Commandery, populationRecordedIn, Book of Han]
-
A.
populationCountedIn
chosen
Indicates that the population of one entity is measured, recorded, or included within the population statistics of another entity.
-
B.
populationIncludes
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
-
C.
populationBasis
Indicates that a population measurement is based on, derived from, or defined with respect to a particular reference, criterion, or underlying basis.
-
D.
permanentPopulation
Indicates that an entity has a stable, long-term resident population rather than a temporary or transient presence.
-
E.
hasRegisteredPopulation
Indicates that an entity has an officially recorded number of inhabitants in a population registry or census.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 8:48 p.m.