Triple
T11871497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Berthing Mechanism |
E282416
|
entity |
| Predicate | standardizedDiameter |
P33679
|
FINISHED |
| Object | approximately 1270 millimeters |
—
|
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 1270 millimeters | Statement: [Common Berthing Mechanism, standardizedDiameter, approximately 1270 millimeters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizedDiameter Context triple: [Common Berthing Mechanism, standardizedDiameter, approximately 1270 millimeters]
-
A.
shellDiameter
Indicates the diameter measurement of a shell, typically specifying the distance across it at its widest point.
-
B.
approximateDiameter
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
-
C.
standardDiscDiameter
chosen
Indicates that one entity specifies the standard diameter measurement of a disc associated with another entity.
-
D.
typicalCaseDiameter
Indicates the usual or standard diameter value associated with an object or case in typical conditions.
-
E.
hasDiameterClass
Indicates that an entity is associated with a specific category or range based on the size of its diameter.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d39d2934819093b9f7006f45e5cb |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:43 p.m.