Triple
T6175348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iota Cancrids |
E137803
|
entity |
| Predicate | observationRequirement |
P8537
|
FINISHED |
| Object | dark, clear skies |
—
|
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: dark, clear skies | Statement: [Iota Cancrids, observationRequirement, dark, clear skies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observationRequirement Context triple: [Iota Cancrids, observationRequirement, dark, clear skies]
-
A.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
B.
visibilityRequirement
chosen
Indicates that one entity must be visible or perceivable under specified conditions for another entity, action, or rule to apply.
-
C.
evaluationRequirement
Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
-
D.
observation
Indicates that one entity perceives, monitors, or takes note of another entity or phenomenon, typically to gather information about it.
-
E.
observedFor
Indicates that one entity is monitored, watched, or examined over a period of time for the benefit or analysis of another entity.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc70ac481909fd1db0d69837eca |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.