Triple
T4449756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Submillimeter Array |
E96378
|
entity |
| Predicate | hasApertureDiameter |
P31648
|
FINISHED |
| Object | 6 meters |
—
|
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: 6 meters | Statement: [Submillimeter Array, hasApertureDiameter, 6 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApertureDiameter Context triple: [Submillimeter Array, hasApertureDiameter, 6 meters]
-
A.
hasAperture
Indicates that one entity possesses or is characterized by a specific opening, gap, or aperture.
-
B.
rearCameraAperture
Indicates the size or f-stop value of the aperture used by a device’s rear-facing camera when capturing images or video.
-
C.
hasApertureClass
Indicates that one entity is classified according to a specific aperture category or class of another entity.
-
D.
objectiveLensDiameter
chosen
Indicates the diameter of the objective lens used in an optical device, such as a camera or telescope.
-
E.
focalLength
Indicates the distance between a lens or mirror and its focal point, determining how strongly it converges or diverges light.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d5975c8190bfe8a2d5d2dbf075 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.