Triple
T20479193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arden Corona |
E502404
|
entity |
| Predicate | primaryDataSource |
P2296
|
FINISHED |
| Object | Voyager 2 narrow-angle camera images |
—
|
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: Voyager 2 narrow-angle camera images | Statement: [Arden Corona, primaryDataSource, Voyager 2 narrow-angle camera images]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDataSource Context triple: [Arden Corona, primaryDataSource, Voyager 2 narrow-angle camera images]
-
A.
primaryDatabase
Indicates that one database serves as the main or authoritative data source in relation to another system or database.
-
B.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
C.
primarySources
chosen
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
-
D.
mainSourceType
Indicates the primary category or kind of source from which something originates or is derived.
-
E.
primaryReference
Indicates that one entity serves as the main or authoritative source of information or citation for 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b54c8188190a71e35fab8d194a6 |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:34 a.m.