Triple
T26657178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VISTA Magellanic Clouds Survey |
E666540
|
entity |
| Predicate | filterUsed |
P88263
|
FINISHED |
| Object | Ks band |
—
|
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: Ks band | Statement: [VISTA Magellanic Clouds Survey, filterUsed, Ks band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filterUsed Context triple: [VISTA Magellanic Clouds Survey, filterUsed, Ks band]
-
A.
usesFilter
chosen
Indicates that one entity applies or employs a filter (such as a criterion, condition, or processing mechanism) to another entity or set of data.
-
B.
filter
Indicates that one entity selectively includes or excludes elements of another entity based on specified criteria or conditions.
-
C.
filterType
Indicates the specific category or method of filtering that is applied to a set of items or data.
-
D.
usesFilterSystem
Indicates that one entity employs or operates a filter system in relation to another entity or context.
-
E.
filterSystem
Indicates that one entity functions to remove or separate unwanted components, substances, or signals from another entity or 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 2:35 a.m.