Triple
T16495123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trachylinae |
E400661
|
entity |
| Predicate | typicalBodyForm |
P3595
|
FINISHED |
| Object | medusa |
—
|
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: medusa | Statement: [Trachylinae, typicalBodyForm, medusa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBodyForm Context triple: [Trachylinae, typicalBodyForm, medusa]
-
A.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
B.
typicalBodyType
chosen
Indicates that one entity is the usual or characteristic body type associated with another entity.
-
C.
establishedBodyType
Indicates that an entity has formally created, founded, or set up a particular organizational body or structure.
-
D.
standardBody
Indicates that an entity conforms to a recognized or officially accepted body type, form, or physical specification.
-
E.
typicalBodyPart
Indicates that one entity is a body part that is characteristically or normally associated with another entity.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e3276b88190946a669b4d893a54 |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.