Triple
T22791408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BTA-6 telescope |
E564119
|
entity |
| Predicate | diameterComparison |
P58619
|
FINISHED |
| Object | larger aperture than Hale Telescope |
—
|
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: larger aperture than Hale Telescope | Statement: [BTA-6 telescope, diameterComparison, larger aperture than Hale Telescope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diameterComparison Context triple: [BTA-6 telescope, diameterComparison, larger aperture than Hale Telescope]
-
A.
approximateDiameter
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
-
B.
円の直径比率
Indicates the proportional relationship between a circle’s diameter and another referenced measure (such as another diameter or a standard length).
-
C.
hasDiameterClass
Indicates that an entity is associated with a specific category or range based on the size of its diameter.
-
D.
bodyDiameter
Indicates the measurement of how wide an object's body is across its broadest cross-section.
-
E.
diameterRank
chosen
Indicates the relative ordering of entities based on the size of their diameters.
- 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c3545fc819084af67cc25e94839 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:30 p.m.