Triple
T25272098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antaresia maculosa |
E633592
|
entity |
| Predicate | reasonForCaptivityPopularity |
P55574
|
FINISHED |
| Object | docile temperament |
—
|
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: docile temperament | Statement: [Antaresia maculosa, reasonForCaptivityPopularity, docile temperament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForCaptivityPopularity Context triple: [Antaresia maculosa, reasonForCaptivityPopularity, docile temperament]
-
A.
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.
-
B.
captivityEnd
Indicates the point in time or event at which an entity’s period of captivity or confinement comes to an end.
-
C.
hasPopularityReason
chosen
Indicates that there is a specific reason or factor explaining why something is popular.
-
D.
periodOfCaptivity
Indicates a time span during which an entity is held in captivity or confinement.
-
E.
heldCaptive
Indicates that one entity is being forcibly confined or restrained by another, preventing their freedom of movement or escape.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 1:16 p.m.