Triple
T23642735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Changqing National Nature Reserve |
E583943
|
entity |
| Predicate | isPartOfRangeOf |
P52888
|
FINISHED |
| Object | giant panda |
—
|
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: giant panda | Statement: [Changqing National Nature Reserve, isPartOfRangeOf, giant panda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfRangeOf Context triple: [Changqing National Nature Reserve, isPartOfRangeOf, giant panda]
-
A.
partOfRange
chosen
Indicates that one entity is included within, or constitutes a segment of, the overall extent or span defined by another entity.
-
B.
includesRange
Indicates that one entity’s span, interval, or range fully contains or covers the span, interval, or range of another entity.
-
C.
rangeIncludes
Indicates that the values or results associated with a property are expected to be of the specified type or types.
-
D.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
E.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b2821cb881909b1ab77aa77208e0 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.