Triple
T15839776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSO-8 (X-ray data) |
E384070
|
entity |
| Predicate | dataLevel |
P67289
|
FINISHED |
| Object | raw data |
—
|
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: raw data | Statement: [OSO-8 (X-ray data), dataLevel, raw data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataLevel Context triple: [OSO-8 (X-ray data), dataLevel, raw data]
-
A.
dataCollectionLevel
chosen
Indicates the extent or granularity at which data is gathered or recorded within a given context or system.
-
B.
classificationLevel
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
-
C.
documentationLevel
Indicates the extent or thoroughness to which something is described, specified, or supported by written or recorded documentation.
-
D.
disclosureLevel
Indicates the extent or degree to which information is revealed, shared, or made accessible in a given context.
-
E.
representationLevel
Indicates the degree or layer at which something stands in for, models, or symbolizes something else (e.g., more concrete vs. more abstract representation).
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e69360819091ea0556bd66d785 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.