Triple
T7459242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atacama Compact Array |
E176201
|
entity |
| Predicate | imagingCapability |
P52562
|
FINISHED |
| Object | sensitive to large angular scales |
—
|
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: sensitive to large angular scales | Statement: [Atacama Compact Array, imagingCapability, sensitive to large angular scales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imagingCapability Context triple: [Atacama Compact Array, imagingCapability, sensitive to large angular scales]
-
A.
hasPhotoFeature
Indicates that an entity possesses a characteristic, capability, or option specifically related to photos or photography.
-
B.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
C.
hasImagingType
chosen
Indicates the specific imaging modality or technique associated with or used in a given imaging procedure or result.
-
D.
displayCapabilities
Indicates the set of functions, features, or behaviors that an entity is able to present or support in a given context.
-
E.
hasAIPhotoFeatures
Indicates that an entity provides or supports photo-related features powered by artificial intelligence.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d332d08190a05c92a00ed09ac6 |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:37 p.m.