Triple
T26564323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Przewalski’s horse |
E666333
|
entity |
| Predicate | captiveBreeding |
P28094
|
FINISHED |
| Object | successful |
—
|
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: successful | Statement: [Przewalski’s horse, captiveBreeding, successful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captiveBreeding Context triple: [Przewalski’s horse, captiveBreeding, successful]
-
A.
reproductionInCaptivity
chosen
Indicates that an organism reproduces successfully while being kept in a controlled or captive environment rather than in the wild.
-
B.
captivePopulation
Indicates that the entities are part of a population kept in captivity, such as in zoos, aquariums, or breeding facilities, rather than living in the wild.
-
C.
breedingCenter
Indicates a relationship where an entity serves as a facility or location dedicated to breeding or reproducing organisms.
-
D.
domesticationCenter
Indicates the place or region where a species was first brought under human control and selectively bred, marking the origin of its domestication.
-
E.
breedingUse
Indicates that one entity is used for breeding or reproductive purposes with respect to another entity.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6149cc0c88190aadaacfa45a2382e |
completed | May 2, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:54 a.m.