Triple
T9808184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RCM |
E238203
|
entity |
| Predicate | revisitTime |
P52563
|
FINISHED |
| Object | 4 days at 30 m resolution |
—
|
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: 4 days at 30 m resolution | Statement: [RCM, revisitTime, 4 days at 30 m resolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisitTime Context triple: [RCM, revisitTime, 4 days at 30 m resolution]
-
A.
hasRevisitTime
chosen
Indicates the interval or schedule at which an entity is revisited, repeated, or observed again.
-
B.
timeSincePreviousVisitMentioned
Indicates that the elapsed time since a previous visit is explicitly referenced or specified in the context.
-
C.
reassessedAfter
Indicates that one entity is evaluated or reviewed again at a time point that occurs after another specified event or assessment.
-
D.
bestVisitedAt
Indicates the optimal time or conditions under which a place or entity should be visited.
-
E.
reappearsAt
Indicates that an entity, after having disappeared or been absent, becomes present again at a specific location or point in 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7ddaac8190a5584a5c863fbaa3 |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.