Triple
T2661286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nepenthes rajah |
E54730
|
entity |
| Predicate | mutualismWith |
P19712
|
FINISHED |
| Object | tree shrews |
—
|
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: tree shrews | Statement: [Nepenthes rajah, mutualismWith, tree shrews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mutualismWith Context triple: [Nepenthes rajah, mutualismWith, tree shrews]
-
A.
notableMutualism
chosen
Indicates a significant mutually beneficial relationship between two entities, where each provides important advantages or services to the other.
-
B.
containsSymbioticAssociationsWith
Indicates that one entity includes or encompasses another entity with which it maintains a symbiotic (mutually dependent or beneficial) biological relationship.
-
C.
bilateralRelation
Indicates a mutual or two-way relationship between two entities, where each affects or interacts with the other.
-
D.
communionWith
Indicates a close, often spiritual or deeply intimate sharing or union between entities, characterized by mutual presence, participation, or fellowship.
-
E.
sharesNatureWith
Indicates that two entities possess the same fundamental characteristics, qualities, or essence.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd9504d10819091abc03532a2fa6d |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.