Triple
T23479900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piedmont, New Mexico |
E570374
|
entity |
| Predicate | populationStatusInStory |
P137692
|
FINISHED |
| Object | largely killed by Andromeda microorganism |
—
|
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: largely killed by Andromeda microorganism | Statement: [Piedmont, New Mexico, populationStatusInStory, largely killed by Andromeda microorganism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationStatusInStory Context triple: [Piedmont, New Mexico, populationStatusInStory, largely killed by Andromeda microorganism]
-
A.
populationState
chosen
Indicates the condition or status of a population at a given point in time, such as its size, distribution, or demographic characteristics.
-
B.
populationIncludes
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
-
C.
populationCount
Indicates the total number of individuals in a specified group, area, or category.
-
D.
populationRole
Indicates the role or function that an entity has within a population or demographic context.
-
E.
userPopulation
Indicates the total number of users associated with or served by a given system, service, or context.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a74f48d8819080e875aaea8b46b3 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:02 p.m.