Triple
T7356101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soo Locks |
E169628
|
entity |
| Predicate | annualTonnage |
P24299
|
FINISHED |
| Object | tens of millions of tons of cargo |
—
|
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: tens of millions of tons of cargo | Statement: [Soo Locks, annualTonnage, tens of millions of tons of cargo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annualTonnage Context triple: [Soo Locks, annualTonnage, tens of millions of tons of cargo]
-
A.
annualCapacity
Indicates the maximum amount of output or throughput an entity can produce or handle within a one-year period.
-
B.
annualContainerThroughputRecordYear
Indicates the specific year in which a record level of annual container throughput was achieved.
-
C.
annualContainerThroughput
Indicates the total volume of containers handled by a facility or system over the course of a year.
-
D.
tonnage
chosen
Indicates the relationship between an object and the measure of its weight or cargo capacity, typically expressed in tons.
-
E.
annualFrom
Indicates that something recurs or is calculated on a yearly basis starting from a specified point in time.
- 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:05 p.m.