Triple
T4007060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhamnus cathartica |
E89549
|
entity |
| Predicate | branchCharacteristic |
P662
|
FINISHED |
| Object | often with thorny tips |
—
|
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: often with thorny tips | Statement: [Rhamnus cathartica, branchCharacteristic, often with thorny tips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchCharacteristic Context triple: [Rhamnus cathartica, branchCharacteristic, often with thorny tips]
-
A.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
B.
selectionCharacteristic
Indicates a distinguishing feature or criterion used to choose or differentiate one entity from others.
-
C.
branchType
Indicates the specific kind or category of branch that an entity belongs to or is associated with.
-
D.
usesLineCharacteristic
Indicates that one entity employs or is based on a specific characteristic or property of a line.
-
E.
branchingPattern
Indicates the structural way in which one element divides into multiple offshoots or subdivisions from a common source.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.