Triple
T17286436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 420 dinghy |
E419666
|
entity |
| Predicate | beam_ft |
P126803
|
FINISHED |
| Object | 5.35 |
—
|
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: 5.35 | Statement: [420 dinghy, beam_ft, 5.35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beam_ft Context triple: [420 dinghy, beam_ft, 5.35]
-
A.
beam
Indicates that one entity emits, directs, or projects a concentrated line or stream (such as light, energy, or information) toward another entity.
-
B.
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.
-
C.
beamApprox
Indicates that one entity is approximately equal to or closely resembles another in value, form, or behavior.
-
D.
beamType
Indicates the specific kind or category of beam involved in the relationship or action.
-
E.
beamComposition
Indicates the constituent particles, materials, or components that make up a given beam.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4378024988190aac6aec006f8f7a1 |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:40 a.m.