Triple
T18258284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diplopoda |
E437274
|
entity |
| Predicate | moistureRequirement |
P32783
|
FINISHED |
| Object | require humid environments |
—
|
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: require humid environments | Statement: [Diplopoda, moistureRequirement, require humid environments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moistureRequirement Context triple: [Diplopoda, moistureRequirement, require humid environments]
-
A.
receivesMoistureFrom
Indicates that one entity obtains or is supplied with moisture (such as water, humidity, or precipitation) from another entity.
-
B.
soilPreference
Indicates the type or condition of soil that an entity prefers or is best suited to grow or exist in.
-
C.
droughtTolerance
Indicates the degree to which an entity can maintain normal function and survival under conditions of limited water availability.
-
D.
isSucculent
Indicates that an entity is a succulent, meaning it has thickened, fleshy tissues adapted for storing water.
-
E.
cultivationRequirement
chosen
Indicates the specific conditions or resources that must be met or provided for something to be successfully cultivated.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd8879e88190893f8da7c3529496 |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.