Triple
T9531778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danionidae |
E229912
|
entity |
| Predicate | typicalBodyShape |
P3595
|
FINISHED |
| Object | slender |
—
|
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: slender | Statement: [Danionidae, typicalBodyShape, slender]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBodyShape Context triple: [Danionidae, typicalBodyShape, slender]
-
A.
typicalBodyType
chosen
Indicates that one entity is the usual or characteristic body type associated with another entity.
-
B.
primaryBodyType
Indicates the main physical form or category that characterizes an entity’s overall body structure or composition.
-
C.
parentBodyType
Indicates that one entity has a body type that serves as the parent or base classification from which another entity's body type is derived or organized.
-
D.
establishedBodyType
Indicates that an entity has formally created, founded, or set up a particular organizational body or structure.
-
E.
typicalFit
Indicates that one entity is a usual, expected, or characteristic match or correspondence for another in a given context.
- 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_69ca8479934c81908006d0e6e970ae05 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98b408648190a04127c1d47fe7d2 |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 8 p.m.