Triple
T2374912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OGLE-I survey |
E46173
|
entity |
| Predicate | timeSampling |
P38785
|
FINISHED |
| Object | multi-epoch observations |
—
|
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: multi-epoch observations | Statement: [OGLE-I survey, timeSampling, multi-epoch observations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSampling Context triple: [OGLE-I survey, timeSampling, multi-epoch observations]
-
A.
timeScaleType
Indicates the type or category of temporal scaling applied to an event, process, or measurement (e.g., real-time, accelerated, aggregated).
-
B.
timeScaleUnit
Indicates the unit of temporal measurement (such as seconds, minutes, or hours) used to express a given time scale.
-
C.
timeIndexed
Indicates that the relationship or property it connects is associated with, or valid during, a specific time or time interval.
-
D.
timescale
Indicates the temporal scale or duration over which a process, relationship, or effect occurs or is evaluated.
-
E.
timingMethod
Indicates the method or technique used to measure or record the timing of an event or process.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69abca4c937c8190b4dfca716b868d4f |
completed | March 7, 2026, 6:48 a.m. |
Created at: March 4, 2026, 7:56 p.m.