Triple
T28198734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nipponia |
E716814
|
entity |
| Predicate | nativeRegionOfNotableSpecies |
P164660
|
FINISHED |
| Object | East 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: East Asia | Statement: [Nipponia, nativeRegionOfNotableSpecies, East Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeRegionOfNotableSpecies Context triple: [Nipponia, nativeRegionOfNotableSpecies, East Asia]
-
A.
notableFaunaRegion
Indicates that a region is known for or characteristically associated with particular notable animal species.
-
B.
habitatOfNotableSpecies
chosen
Indicates that a location serves as the natural environment or living area for one or more notable species.
-
C.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
-
D.
naturalRegionOf
Indicates that one entity is the natural geographic region or area in which the other entity is located or to which it belongs.
-
E.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 10:29 p.m.