Triple
T457983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altmark |
E7273
|
entity |
| Predicate | displacementApproximate |
P7301
|
FINISHED |
| Object | about 20,000 tons |
—
|
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: about 20,000 tons | Statement: [Altmark, displacementApproximate, about 20,000 tons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displacementApproximate Context triple: [Altmark, displacementApproximate, about 20,000 tons]
-
A.
displacement
Indicates a change in an entity’s position from one location to another, typically specifying both direction and magnitude of that movement.
-
B.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
C.
approximateMass
chosen
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
D.
approximateDiameter
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
-
E.
approximationType
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efa3163081909acff040a22bd559 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede614b88190be07425f5535f56d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.