Triple
T1541319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atacama Large Millimeter/submillimeter Array |
E32871
|
entity |
| Predicate | maximumBaseline |
P22930
|
FINISHED |
| Object | about 16 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 16 kilometers | Statement: [Atacama Large Millimeter/submillimeter Array, maximumBaseline, about 16 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumBaseline Context triple: [Atacama Large Millimeter/submillimeter Array, maximumBaseline, about 16 kilometers]
-
A.
maximumExtentFromBaseline
Indicates the greatest distance or deviation of something from a defined baseline reference.
-
B.
baselineType
Indicates the type or category of a baseline used as a reference point for comparison or evaluation.
-
C.
maximumDraft
Indicates that there is an upper limit on the number of drafts that can be created, stored, or associated with a given entity or process.
-
D.
maximumService
Indicates that an entity provides the highest allowable or achievable level of service within a given context or system.
-
E.
maximumExtent
chosen
Indicates the greatest or furthest degree, size, or range to which something can extend or apply within a given context.
- 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_69a885ed29088190a3c2d5a3d100c16e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa95c1a2948190a2b98469afec1a7d |
completed | March 6, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69a907b2453c8190a41f6b88c8217d1e |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.