Triple
T35723537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melanochelys |
E1032545
|
entity |
| Predicate | hasHeadRetractionMode |
P50706
|
FINISHED |
| Object | cryptodiran neck retraction |
—
|
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: cryptodiran neck retraction | Statement: [Melanochelys, hasHeadRetractionMode, cryptodiran neck retraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadRetractionMode Context triple: [Melanochelys, hasHeadRetractionMode, cryptodiran neck retraction]
-
A.
headRetraction
chosen
Indicates a relationship where an entity pulls or draws its head back from a previous position.
-
B.
hasRetractablePitch
Indicates that an entity (typically a stadium or venue) possesses a playing surface or pitch that can be mechanically extended or withdrawn as needed.
-
C.
hasRearUnitType
Indicates that an entity’s rear section or back part is of a specified type.
-
D.
hasHeadPosition
Indicates the specific spatial position or orientation of an entity’s head relative to a reference frame or context.
-
E.
hasHeadNear
Indicates that one entity’s head is positioned close to another entity or reference point in space.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 3, 2026, 4:05 p.m.