Triple
T7118846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern China Collection |
E165892
|
entity |
| Predicate | hasLivingSpecimens |
P74675
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Southern China Collection, hasLivingSpecimens, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLivingSpecimens Context triple: [Southern China Collection, hasLivingSpecimens, true]
-
A.
hasLivingSpecies
Indicates that an entity currently contains, supports, or is associated with one or more species that are alive or extant.
-
B.
hasNotableSpecimen
Indicates that an entity possesses or is associated with a specimen that is considered particularly significant, remarkable, or noteworthy.
-
C.
hasExhibitSpecies
Indicates that an exhibit or display includes or features a particular species.
-
D.
hasWildPopulationOf
Indicates that a location or area contains a naturally occurring, non-captive population of the specified species.
-
E.
containsWildSpecies
Indicates that one entity includes, houses, or encompasses wild (non-domesticated) species within its scope or boundaries.
- F. None of above. chosen
Provenance (4 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e61b8a288190a165ea25adfaaef5 |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e456e89481908df42a1b4232a4a0 |
completed | March 27, 2026, 8:11 p.m. |
Created at: March 27, 2026, 2:43 p.m.