Triple
T11843827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caribbean spiny lobster |
E281721
|
entity |
| Predicate | lacksBodyPart |
P101817
|
FINISHED |
| Object | large front claws |
—
|
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: large front claws | Statement: [Caribbean spiny lobster, lacksBodyPart, large front claws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lacksBodyPart Context triple: [Caribbean spiny lobster, lacksBodyPart, large front claws]
-
A.
skeletonLacks
Indicates that an entity’s skeleton does not possess or is missing a specified bone, feature, or structural component.
-
B.
hasLimb
Indicates that an entity possesses a specific limb as part of its body.
-
C.
lostLimb
Indicates that an entity has had one or more of its limbs removed or rendered permanently absent, typically as a result of injury, surgery, or trauma.
-
D.
lostLimbTo
Indicates that one entity has had a limb removed, severed, or rendered nonfunctional as a direct result of another entity or cause.
-
E.
injuredBodyPart
Indicates that an entity has sustained an injury specifically affecting a particular body part.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65a597c8190b09f57463b279afc |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.