Triple
T18329723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Submillimeter Array |
E439106
|
entity |
| Predicate | hasAntennaDiameter |
P12573
|
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, hasAntennaDiameter, 6 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAntennaDiameter Context triple: [Submillimeter Array, hasAntennaDiameter, 6 meters]
-
A.
hasExternalAntenna
Indicates that an entity is equipped with or connected to an antenna located outside its main body or enclosure.
-
B.
antennaType
Indicates the specific kind or category of antenna associated with an entity or connection.
-
C.
highGainAntennaDiameter
chosen
Indicates the physical diameter measurement of a high-gain antenna associated with an entity.
-
D.
bodyDiameter
Indicates the measurement of how wide an object's body is across its broadest cross-section.
-
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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ec900808190bc4468270e0957c1 |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.