Triple
T18843053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 6704 |
E460843
|
entity |
| Predicate | catalogEntryType |
P24430
|
FINISHED |
| Object | deep-sky object |
—
|
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: deep-sky object | Statement: [NGC 6704, catalogEntryType, deep-sky object]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogEntryType Context triple: [NGC 6704, catalogEntryType, deep-sky object]
-
A.
catalogueType
chosen
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
B.
labelCatalogType
Indicates that an entity is assigned a specific catalog type label, defining its classification within a cataloging system.
-
C.
catalogCategory
Indicates that an item or entity is assigned to, or belongs within, a specific catalog category.
-
D.
catalog
Indicates the action of systematically listing, organizing, or recording items or information into a structured collection or database.
-
E.
catalogName
Indicates that an entity has a specific catalog designation or title by which it is listed or identified.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8eb32548190b2313e877f6ff179 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.