Triple
T26710050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elachuridae |
E673386
|
entity |
| Predicate | morphologicalTraits |
P161608
|
FINISHED |
| Object | short rounded wings |
—
|
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: short rounded wings | Statement: [Elachuridae, morphologicalTraits, short rounded wings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: morphologicalTraits Context triple: [Elachuridae, morphologicalTraits, short rounded wings]
-
A.
morphologicalTraits
chosen
Indicates a relationship where specific physical form or structural characteristics are attributed to or associated with an entity.
-
B.
morphologicalDiversity
Indicates variation in the forms, structures, or shapes of entities within a group or system.
-
C.
morphologicalComparison
Indicates a relationship where two or more entities are compared based on differences or similarities in their morphological (form or structural) characteristics.
-
D.
distinguishingTrait
Indicates that a particular characteristic or feature uniquely differentiates one entity from another.
-
E.
relatedMorphologicalFeature
Indicates that one entity is connected to another through a shared or corresponding morphological feature or structure.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 3:35 a.m.