Triple
T31347087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rev-9 |
E799475
|
entity |
| Predicate | canSeparateInto |
P12217
|
FINISHED |
| Object | solid endoskeleton |
—
|
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: solid endoskeleton | Statement: [Rev-9, canSeparateInto, solid endoskeleton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSeparateInto Context triple: [Rev-9, canSeparateInto, solid endoskeleton]
-
A.
canBeSplitAmong
Indicates that something is divisible into parts that can be distributed among multiple recipients or groups.
-
B.
separatedInto
chosen
Indicates that something has been divided or split into distinct parts, groups, or components.
-
C.
canSplit
Indicates that an entity has the ability or is allowed to divide something into two or more parts.
-
D.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
E.
separatedIn
Indicates that two or more entities, once together or associated, have been divided, split, or otherwise placed into distinct parts, groups, or locations.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f18afd48190bbbd54e517946499 |
completed | May 3, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:17 p.m.