Triple
T13179034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LAT |
E313676
|
entity |
| Predicate | scanningStrategy |
P17347
|
FINISHED |
| Object | covers entire sky every few hours |
—
|
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: covers entire sky every few hours | Statement: [LAT, scanningStrategy, covers entire sky every few hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scanningStrategy Context triple: [LAT, scanningStrategy, covers entire sky every few hours]
-
A.
acquisitionStrategy
Indicates the method or approach by which one entity acquires or gains control, ownership, or access to another entity.
-
B.
scanDirection
Indicates the direction or orientation in which a scanning action is performed or data is acquired.
-
C.
scanningLaw
Indicates that an entity is subject to, governed by, or defined through a legal rule or regulation concerning scanning activities or processes.
-
D.
scanType
chosen
Indicates the specific kind or category of scanning operation performed or required in a given context.
-
E.
scans
Indicates performing a systematic examination or inspection of something, often using a device or method to detect, read, or analyze its contents or structure.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.