Triple
T28127466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drepung Monastery |
E710967
|
entity |
| Predicate | peakMonkPopulation |
P101078
|
FINISHED |
| Object | around 10000 monks |
—
|
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: around 10000 monks | Statement: [Drepung Monastery, peakMonkPopulation, around 10000 monks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakMonkPopulation Context triple: [Drepung Monastery, peakMonkPopulation, around 10000 monks]
-
A.
monitoredPopulation
Indicates that a given group or population is being systematically observed, tracked, or measured by another entity.
-
B.
peakPopulationApproximate
chosen
Indicates that the peak population of an entity is known only approximately rather than as an exact value.
-
C.
lastKnownPopulations
Indicates the most recently recorded population counts associated with an entity or set of entities.
-
D.
populationAtPeak
Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
-
E.
populationCount
Indicates the total number of individuals in a specified group, area, or category.
- 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f640fd4f1c8190906450e47fb29281 |
completed | May 2, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:21 p.m.