Triple
T27053553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasua narica |
E684840
|
entity |
| Predicate | geographicVariation |
P32680
|
FINISHED |
| Object | several subspecies described |
—
|
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: several subspecies described | Statement: [Nasua narica, geographicVariation, several subspecies described]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicVariation Context triple: [Nasua narica, geographicVariation, several subspecies described]
-
A.
geographicDistribution
Indicates the spatial range or area over which something occurs, exists, or is found.
-
B.
geographicRangeType
Indicates the kind of geographic range or distribution pattern that characterizes where an entity occurs or is found.
-
C.
haveLandAreaVariation
Indicates that an entity’s land area changes over time or differs across contexts or measurements.
-
D.
geographicRangeTrend
Indicates how the spatial extent or distribution area of something is changing over time (e.g., expanding, contracting, or remaining stable).
-
E.
hasRegionalVariationsIn
chosen
Indicates that something exhibits different forms, versions, or characteristics depending on the geographic region.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 8:15 a.m.