Triple
T25557995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dover Bronze Age Boat |
E640626
|
entity |
| Predicate | beamEstimate |
P158644
|
FINISHED |
| Object | approximately 2.3 metres |
—
|
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 2.3 metres | Statement: [Dover Bronze Age Boat, beamEstimate, approximately 2.3 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beamEstimate Context triple: [Dover Bronze Age Boat, beamEstimate, approximately 2.3 metres]
-
A.
beam_ft
Indicates a relationship where something is measured, specified, or characterized in terms of its beam width or span expressed in feet.
-
B.
beamApprox
Indicates that one entity is approximately equal to or closely resembles another in value, form, or behavior.
-
C.
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.
-
D.
beamPlanned
Indicates that a beam has been scheduled or intended to be delivered, constructed, or activated at a specified time or context.
-
E.
displacementEstimate
Indicates an estimated amount or measure of how far something has moved or shifted from its original position.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8cb186c819099b247e4a8cbd367 |
completed | May 2, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 3:44 p.m.