Triple
T5837894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fram |
E129517
|
entity |
| Predicate | hullShape |
P8584
|
FINISHED |
| Object | rounded to be squeezed up by ice |
—
|
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: rounded to be squeezed up by ice | Statement: [Fram, hullShape, rounded to be squeezed up by ice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hullShape Context triple: [Fram, hullShape, rounded to be squeezed up by ice]
-
A.
hullType
chosen
Indicates the specific structural design or configuration of an object's hull, typically classifying how its outer body or shell is shaped or constructed.
-
B.
hullConstruction
Indicates the process or activity of building, assembling, or forming the main body (hull) of a vessel or similar structure.
-
C.
hullLayout
Indicates how the structural arrangement or configuration of a vessel’s hull is organized or laid out in relation to its components.
-
D.
hullColor
Indicates the color attribute assigned to the outer surface (hull) of an object, typically a vehicle or vessel.
-
E.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.