Triple
T31724147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hedinichthys |
E809662
|
entity |
| Predicate | nativeRangeRegion |
P4570
|
FINISHED |
| Object | Central Asia |
—
|
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: Central Asia | Statement: [Hedinichthys, nativeRangeRegion, Central Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeRangeRegion Context triple: [Hedinichthys, nativeRangeRegion, Central Asia]
-
A.
nativeRange
chosen
Indicates the geographic area where an entity naturally occurs or originated without human introduction.
-
B.
nativeRangeType
Indicates the specific type or classification of the geographic area where an entity naturally occurs or originates.
-
C.
rangeRegion
Indicates that one entity defines or corresponds to the spatial or conceptual region over which another entity extends or is applicable.
-
D.
nativeRegionOfMembers
Indicates the geographic region from which the members of a group or organization originally come.
-
E.
isoRangeNative
Indicates that two values fall within the same native ISO-defined range or interval, according to the system’s inherent ISO-based scale or categorization.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 30, 2026, 11:19 p.m.