Triple
T29767373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aframax |
E753950
|
entity |
| Predicate | hasTypicalDraftRange |
P195272
|
FINISHED |
| Object | 14–15 meters (approximate) |
—
|
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: 14–15 meters (approximate) | Statement: [Aframax, hasTypicalDraftRange, 14–15 meters (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalDraftRange Context triple: [Aframax, hasTypicalDraftRange, 14–15 meters (approximate)]
-
A.
typicalDraft
Indicates that something represents the standard or commonly expected version or form of a draft within a given context.
-
B.
draftedAfter
Indicates that one entity was selected or formally drafted at a later time than another entity.
-
C.
draftedInPeriod
Indicates that an entity was formally drafted or selected during a specified time period.
-
D.
hasDraftedPlayersTo
Indicates that one entity has selected or drafted players to join or belong to another entity, such as a team, league, or organization.
-
E.
hasJuniorDraftEligibility
Indicates that an individual meets the criteria to be eligible for selection in a junior-level draft.
- F. None of above. chosen
Provenance (4 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_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
| PDg | Predicate description generation | batch_69fdb4544b548190b8971f8055d48caa |
completed | May 8, 2026, 10 a.m. |
Created at: April 28, 2026, 8:39 p.m.