Triple
T18045271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cylindromyrmex |
E431754
|
entity |
| Predicate | bodyFormAdaptation |
P129604
|
FINISHED |
| Object | adapted for narrow spaces |
—
|
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: adapted for narrow spaces | Statement: [Cylindromyrmex, bodyFormAdaptation, adapted for narrow spaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyFormAdaptation Context triple: [Cylindromyrmex, bodyFormAdaptation, adapted for narrow spaces]
-
A.
bodyConfiguration
Indicates the specific physical arrangement, posture, or structural setup of an entity’s body in relation to its parts or environment.
-
B.
bodyTransformation
Indicates a change in an entity’s physical form, structure, or appearance into a different bodily state.
-
C.
bodyAssembly
Indicates that one entity is the assembled physical body or structural configuration composed from the parts or components represented by another entity.
-
D.
nativeForm
Indicates that one entity is the original or native linguistic form of another, such as a word’s form in its source language.
-
E.
bodyPattern
Indicates a recurring or characteristic configuration, arrangement, or sequence exhibited by a body or physical form.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bff202088190ae971879348e2294 |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:25 a.m.