Triple
T20765554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paliurus australis |
E511085
|
entity |
| Predicate | hasBranchCharacteristic |
P141435
|
FINISHED |
| Object | spiny branches |
—
|
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: spiny branches | Statement: [Paliurus australis, hasBranchCharacteristic, spiny branches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBranchCharacteristic Context triple: [Paliurus australis, hasBranchCharacteristic, spiny branches]
-
A.
hasBranches
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
-
B.
hasBankCharacteristic
Indicates that a bank possesses a particular attribute, feature, or quality.
-
C.
hasBranchName
Indicates that an entity (such as a branch or subdivision) bears or is identified by a specific branch name.
-
D.
hasTradeCharacteristic
Indicates that an entity possesses a specific trade-related attribute, quality, or feature.
-
E.
isPartOfBranchTypically
Indicates that something is typically a component or subdivision within a larger branch.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24bde0c8190b46986b89bf2e037 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:36 p.m.