Triple
T7272468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Very Long Baseline Array |
E161138
|
entity |
| Predicate | maximumBaselineLength |
P49994
|
FINISHED |
| Object | about 8600 kilometers |
—
|
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: about 8600 kilometers | Statement: [Very Long Baseline Array, maximumBaselineLength, about 8600 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumBaselineLength Context triple: [Very Long Baseline Array, maximumBaselineLength, about 8600 kilometers]
-
A.
hasBaselineLength
chosen
Indicates that one entity has a specified baseline length measurement in relation to another entity or reference.
-
B.
maximumExtentFromBaseline
Indicates the greatest distance or deviation of something from a defined baseline reference.
-
C.
maximumSegmentLength
Indicates the greatest allowable or observed length of a segment within a given context or structure.
-
D.
baseLengthOriginal
Indicates the original or initial length value of a base element before any changes or transformations.
-
E.
minimumWidth
Indicates that there is a specified smallest allowable or required width for something in the relationship.
- 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_69c6885181008190b419040e22939c7c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:58 p.m.