Triple
T4449777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Submillimeter Array |
E96378
|
entity |
| Predicate | hasMaximumBaseline |
P49994
|
FINISHED |
| Object | approximately 508 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: approximately 508 meters | Statement: [Submillimeter Array, hasMaximumBaseline, approximately 508 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumBaseline Context triple: [Submillimeter Array, hasMaximumBaseline, approximately 508 meters]
-
A.
hasBaselineLength
chosen
Indicates that one entity has a specified baseline length measurement in relation to another entity or reference.
-
B.
hasMaximumValue
Indicates that one value in a set is the greatest or highest possible according to a specified criterion.
-
C.
maximumExtentFromBaseline
Indicates the greatest distance or deviation of something from a defined baseline reference.
-
D.
isMaximumWhen
Indicates that a quantity or function reaches its greatest possible value under specified conditions or at a particular point.
-
E.
hasMaximumGrade
Indicates that an entity possesses the highest possible grade or score within a defined grading or evaluation system.
- 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.