Triple
T250737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bathyscaphe Trieste |
E5140
|
entity |
| Predicate | pressureSphereMaterial |
P618
|
FINISHED |
| Object | steel |
—
|
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: steel | Statement: [bathyscaphe Trieste, pressureSphereMaterial, steel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pressureSphereMaterial Context triple: [bathyscaphe Trieste, pressureSphereMaterial, steel]
-
A.
surfaceType
Indicates the kind or classification of surface associated with an entity or interaction.
-
B.
pressureAtBottom
Indicates that a specified amount of pressure is exerted or present at the bottom of a given object, container, or region.
-
C.
material
chosen
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
-
D.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
E.
collider
Indicates that two or more entities participate together in operating or utilizing a particle collider or similar high-energy physics experimental facility.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d38aba8819081d0958eb60ce27e |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.