Triple
T20391439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-850 |
E498093
|
entity |
| Predicate | hasEndoskeleton |
P139942
|
FINISHED |
| Object | hyperalloy combat chassis |
—
|
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: hyperalloy combat chassis | Statement: [T-850, hasEndoskeleton, hyperalloy combat chassis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndoskeleton Context triple: [T-850, hasEndoskeleton, hyperalloy combat chassis]
-
A.
hasMantleCavity
Indicates that an organism possesses a mantle cavity, a body space formed by the mantle that typically houses gills, excretory openings, and other organs.
-
B.
hasSpines
Indicates that one entity possesses or is characterized by spines or spine-like structures.
-
C.
hasForelimbs
Indicates that an entity possesses front limbs or appendages used for movement, manipulation, or support.
-
D.
hasLimbs
Indicates that an entity possesses one or more limbs as physical appendages.
-
E.
hasCarapace
Indicates that an entity possesses a hard, protective outer shell or covering (a carapace).
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6790f8d9c819093038f6bb6f47a92 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:28 a.m.