Triple
T16390755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crematogaster |
E398043
|
entity |
| Predicate | interactionWithPlants |
P3806
|
FINISHED |
| Object | forms mutualisms with myrmecophytic plants in some regions |
—
|
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: forms mutualisms with myrmecophytic plants in some regions | Statement: [Crematogaster, interactionWithPlants, forms mutualisms with myrmecophytic plants in some regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactionWithPlants Context triple: [Crematogaster, interactionWithPlants, forms mutualisms with myrmecophytic plants in some regions]
-
A.
involvesPlant
chosen
Indicates that the relationship or action includes or pertains to a plant as a participating entity.
-
B.
plantCollection
Indicates that one entity maintains or possesses a collection of plants, typically grouped or curated as a set.
-
C.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
D.
containsPlantsWith
Indicates that one entity includes or holds within it one or more plant entities.
-
E.
isHouseplant
Indicates that an entity is a plant typically grown and kept indoors as a houseplant.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e326425c8081908cacffcfa8c7386b |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.