Triple
T17477420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remipedia |
E425574
|
entity |
| Predicate | trunkSegments |
P127608
|
FINISHED |
| Object | numerous similar trunk segments |
—
|
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: numerous similar trunk segments | Statement: [Remipedia, trunkSegments, numerous similar trunk segments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trunkSegments Context triple: [Remipedia, trunkSegments, numerous similar trunk segments]
-
A.
hasTrunk
Indicates that one entity possesses or is equipped with a trunk as a physical feature or component.
-
B.
trunkVolume
Indicates the volume or capacity of an entity’s trunk or main storage compartment.
-
C.
trunkCharacteristic
Indicates a relationship where a specific characteristic or property is attributed to a trunk (such as that of a tree or similar object).
-
D.
supportsTrunks
Indicates that one entity provides structural or functional support to the trunks of another entity.
-
E.
trunkPrefix
Indicates that one entity serves as the initial, leading segment or prefix of another entity, often in a hierarchical or concatenated structure.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451bd865081909b5f84405c40ff14 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:47 a.m.