Triple
T29767372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aframax |
E753950
|
entity |
| Predicate | hasTypicalBeamRange |
P195230
|
FINISHED |
| Object | 40–44 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: 40–44 meters (approximate) | Statement: [Aframax, hasTypicalBeamRange, 40–44 meters (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalBeamRange Context triple: [Aframax, hasTypicalBeamRange, 40–44 meters (approximate)]
-
A.
hasTypicalBeam
Indicates that an entity is associated with a characteristic or standard type of beam it commonly uses or possesses.
-
B.
hasBeamSpecies
Indicates a relationship where an object or structure possesses or is associated with a particular type or species of beam.
-
C.
hasHorizontalBeamPosition
Indicates the relative placement or alignment of a horizontal beam with respect to a reference structure or coordinate system.
-
D.
hasBeamlines
Indicates that one entity possesses, contains, or is associated with one or more beamlines.
-
E.
hasVerticalBeamLength
Indicates that an entity is associated with a vertical beam whose length is specified.
- 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_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
| PDg | Predicate description generation | batch_69fdb3172b808190b590d7c5be31ebb7 |
completed | May 8, 2026, 9:55 a.m. |
Created at: April 28, 2026, 8:39 p.m.