Triple
T28711336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APT |
E729838
|
entity |
| Predicate | imageScanDirection |
P35105
|
FINISHED |
| Object | along satellite ground track |
—
|
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: along satellite ground track | Statement: [APT, imageScanDirection, along satellite ground track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imageScanDirection Context triple: [APT, imageScanDirection, along satellite ground track]
-
A.
scanDirection
chosen
Indicates the direction or orientation in which a scanning action is performed or data is acquired.
-
B.
scanType
Indicates the specific kind or category of scanning operation performed or required in a given context.
-
C.
scanFormat
Indicates the format or pattern used when scanning or parsing input data.
-
D.
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.
-
E.
usesScanningMethod
Indicates that an entity performs or carries out an action by employing a specific scanning method.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 5:48 a.m.