Triple
T29767369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aframax |
E753950
|
entity |
| Predicate | hasAlternativeClassificationBasis |
P34582
|
FINISHED |
| Object | freight rate scale |
—
|
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: freight rate scale | Statement: [Aframax, hasAlternativeClassificationBasis, freight rate scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeClassificationBasis Context triple: [Aframax, hasAlternativeClassificationBasis, freight rate scale]
-
A.
hasAlternativeBasis
Indicates that something is supported, justified, or founded on a different underlying reason, source, or principle than the primary or original one.
-
B.
basisOfClassification
chosen
Indicates that one entity serves as the criterion or foundation used to classify or categorize another entity.
-
C.
hasAlternativeReferent
Indicates that an entity can also be referred to or identified by an alternative name, label, or reference.
-
D.
hasAlternativeNotation
Indicates that an entity can be represented or written in a different, equivalent form or notation.
-
E.
isAlternativeTo
Indicates that one entity can serve as a substitute or different option in place of another.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 28, 2026, 8:39 p.m.