Triple
T2374914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OGLE-I survey |
E46173
|
entity |
| Predicate | dataUsage |
P399
|
FINISHED |
| Object | study of stellar variability |
—
|
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: study of stellar variability | Statement: [OGLE-I survey, dataUsage, study of stellar variability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataUsage Context triple: [OGLE-I survey, dataUsage, study of stellar variability]
-
A.
dataUse
chosen
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
-
B.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
C.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
D.
dataRateGeneration
Indicates the rate at which data is produced or generated over time in a given context.
-
E.
trackUsage
Indicates that one entity monitors and records how another entity or resource is being used over time.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.