Triple
T6118602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingfisher |
E136422
|
entity |
| Predicate | hasMorphologyAdaptation |
P2375
|
FINISHED |
| Object | streamlined body for diving |
—
|
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: streamlined body for diving | Statement: [Kingfisher, hasMorphologyAdaptation, streamlined body for diving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMorphologyAdaptation Context triple: [Kingfisher, hasMorphologyAdaptation, streamlined body for diving]
-
A.
isFrequentlyAdapted
Indicates that a work or source material is often transformed or re-created into new formats or versions, such as films, plays, or other media.
-
B.
adaptationType
chosen
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
C.
modifiesMorphologyOf
Indicates that one entity alters or changes the morphological structure or form of another entity.
-
D.
adaptationStatus
Indicates the current state or progress of how something has been adapted or adjusted in response to specific conditions, requirements, or contexts.
-
E.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bec9b8c8190b3268b0ba952aae6 |
completed | March 22, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.