Triple
T15580422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jubaea chilensis |
E374479
|
entity |
| Predicate | hasTrunkType |
P46315
|
FINISHED |
| Object | single, massive, columnar trunk |
—
|
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: single, massive, columnar trunk | Statement: [Jubaea chilensis, hasTrunkType, single, massive, columnar trunk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrunkType Context triple: [Jubaea chilensis, hasTrunkType, single, massive, columnar trunk]
-
A.
hasTrunk
Indicates that one entity possesses or is equipped with a trunk as a physical feature or component.
-
B.
trunkCharacteristic
chosen
Indicates a relationship where a specific characteristic or property is attributed to a trunk (such as that of a tree or similar object).
-
C.
hasTrunkCarvings
Indicates that an entity (typically a tree) possesses carvings or engravings on its trunk.
-
D.
supportsTrunks
Indicates that one entity provides structural or functional support to the trunks of another entity.
-
E.
isOnTrunkLine
Indicates that something is located on, or directly connected to, a primary or main trunk line within a network or system.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e24064c8190b132c3092877fbfa |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.