Triple
T23556293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Choisya |
E578193
|
entity |
| Predicate | toleratesPruning |
P109525
|
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: [Choisya, toleratesPruning, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toleratesPruning Context triple: [Choisya, toleratesPruning, true]
-
A.
pruningTolerance
chosen
Indicates how well an entity can withstand or recover from being cut back, trimmed, or pruned.
-
B.
pruningType
Indicates the specific method or style of pruning applied to an entity (e.g., how it is cut back or trimmed).
-
C.
terminationPolicyApplied
Indicates that a specific termination policy has been enforced or put into effect for the related entity or relationship.
-
D.
pruningTime
Indicates the time or period during which a pruning action is performed on something.
-
E.
tolerates
Indicates that one entity endures, accepts, or allows the presence, behavior, or condition of another entity without intervening to stop or change it.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aed37f248190992f040f4d22f0bf |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:12 p.m.