Triple
T33239172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christensenia |
E850914
|
entity |
| Predicate | fruitPresence |
P176239
|
FINISHED |
| Object | lacks fruits |
—
|
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: lacks fruits | Statement: [Christensenia, fruitPresence, lacks fruits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fruitPresence Context triple: [Christensenia, fruitPresence, lacks fruits]
-
A.
fruitAdheresTo
Indicates that a fruit is physically attached or sticks to another surface or object.
-
B.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
-
C.
occursInDevice
Indicates that an event, process, or phenomenon takes place within or inside a specified device.
-
D.
hasFruitType
Indicates that an entity possesses or is associated with a specific type or category of fruit.
-
E.
kitAvailability
Indicates that a particular kit is available for use, access, or distribution in a given context.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6dd3b335481909e24d4eb5b0269f9 |
completed | May 3, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:31 a.m.