Triple
T30815632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sichuan Giant Panda Sanctuaries |
E784767
|
entity |
| Predicate | containsHabitatOf |
P71977
|
FINISHED |
| Object | giant panda |
—
|
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: giant panda | Statement: [Sichuan Giant Panda Sanctuaries, containsHabitatOf, giant panda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsHabitatOf Context triple: [Sichuan Giant Panda Sanctuaries, containsHabitatOf, giant panda]
-
A.
containsSpeciesWithHabitat
chosen
Indicates that an entity includes one or more species that are associated with a particular habitat.
-
B.
hasAssociatedHabitat
Indicates that an entity is linked to a particular habitat in which it typically lives, occurs, or is found.
-
C.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
-
D.
usesHabitatFeature
Indicates that an organism makes use of a particular habitat feature (such as a structure, resource, or microhabitat) as part of its behavior or life history.
-
E.
cohabitsWith
Indicates that two entities live together in the same dwelling or shared residence.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
Created at: April 29, 2026, 8:43 p.m.