Triple
T37145057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICCN |
E920219
|
entity |
| Predicate | notableProtectedSpecies |
P77745
|
FINISHED |
| Object | mountain gorilla |
—
|
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: mountain gorilla | Statement: [ICCN, notableProtectedSpecies, mountain gorilla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProtectedSpecies Context triple: [ICCN, notableProtectedSpecies, mountain gorilla]
-
A.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
-
B.
notableSpeciesGroup
Indicates that an entity is a significant or characteristic member of a particular species group associated with another entity.
-
C.
habitatOfNotableSpecies
Indicates that a location serves as the natural environment or living area for one or more notable species.
-
D.
hasProtectedSpecies
chosen
Indicates that the subject contains, supports, or is associated with one or more species that are legally or formally designated as protected.
-
E.
naturalReservoirOfNotableSpecies
Indicates that a location serves as a natural habitat or reservoir for one or more notable species.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.