Triple
T25557994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dover Bronze Age Boat |
E640626
|
entity |
| Predicate | originalLengthEstimate |
P115508
|
FINISHED |
| Object | approximately 15 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 15 metres | Statement: [Dover Bronze Age Boat, originalLengthEstimate, approximately 15 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalLengthEstimate Context triple: [Dover Bronze Age Boat, originalLengthEstimate, approximately 15 metres]
-
A.
estimatedOriginalLength
chosen
Indicates the approximated or inferred length that something originally had before any changes, damage, or loss.
-
B.
usableLength
Indicates the portion of an object’s total length that can actually be used for its intended function or purpose.
-
C.
outputLength
Indicates the length or size of the result produced by a process, function, or operation.
-
D.
reportedLength
Indicates the length value that has been stated, recorded, or communicated for something, rather than one directly measured or verified.
-
E.
hasAlternativeLengthEstimate
Indicates that there exists another, differing estimate for the length of the same entity or feature.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 21, 2026, 3:44 p.m.