Triple
T19385769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akademik Lomonosov |
E484929
|
entity |
| Predicate | displacement_tonnes |
P98591
|
FINISHED |
| Object | about 21500 |
—
|
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 21500 | Statement: [Akademik Lomonosov, displacement_tonnes, about 21500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displacement_tonnes Context triple: [Akademik Lomonosov, displacement_tonnes, about 21500]
-
A.
deadweightTonnage
Indicates the total carrying capacity of a vessel, measured as the maximum weight of cargo, fuel, passengers, provisions, and other loads it can safely transport.
-
B.
standardDisplacement
Indicates the typical or officially specified amount of displacement (such as volume, weight, or capacity) associated with an entity under standard conditions.
-
C.
tonnage
Indicates the relationship between an object and the measure of its weight or cargo capacity, typically expressed in tons.
-
D.
estimatedMassInTonnes
chosen
Indicates the approximate mass of an entity expressed in metric tonnes.
-
E.
grossTonnage
Indicates the total internal volume or carrying capacity of a vessel, measured in gross tons, as defined by maritime tonnage rules.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b40d1148190b4fcd9ad56aa6910 |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.