Triple
T9562930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T2 tanker |
E230718
|
entity |
| Predicate | typicalBeam |
P6098
|
FINISHED |
| Object | approximately 68 feet |
—
|
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: approximately 68 feet | Statement: [T2 tanker, typicalBeam, approximately 68 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBeam Context triple: [T2 tanker, typicalBeam, approximately 68 feet]
-
A.
hasTypicalBeam
chosen
Indicates that an entity is associated with a characteristic or standard type of beam it commonly uses or possesses.
-
B.
beamType
Indicates the specific kind or category of beam involved in the relationship or action.
-
C.
beam
Indicates that one entity emits, directs, or projects a concentrated line or stream (such as light, energy, or information) toward another entity.
-
D.
beamUse
Indicates the action of directing or emitting a beam (such as light, energy, or signal) from one entity toward a target or in a specific direction.
-
E.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9965e7b881909df98e933db38092 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:03 p.m.