Triple
T6232078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polar bear |
E139379
|
entity |
| Predicate | bodyAdaptation |
P2375
|
FINISHED |
| Object | thick layer of blubber |
—
|
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: thick layer of blubber | Statement: [Polar bear, bodyAdaptation, thick layer of blubber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyAdaptation Context triple: [Polar bear, bodyAdaptation, thick layer of blubber]
-
A.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
-
B.
adaptationType
chosen
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
C.
adaptationStyle
Indicates how an entity adjusts or modifies its behavior, form, or strategy in response to changing conditions or influences.
-
D.
adaptationSubject
Indicates that one entity serves as the source or subject matter that is adapted into another work or form.
-
E.
adaptationDetail
Indicates that additional information is provided about how something has been adapted or modified from its original form.
- 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_69c008b0e7ac8190808a59573ee646f3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062ee6f088190bf72692eb8ffb761 |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.