Triple
T22710635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Dunlap Observatory (DDO) catalog |
E561583
|
entity |
| Predicate | catalogsType |
P24430
|
FINISHED |
| Object | galaxies |
—
|
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: galaxies | Statement: [David Dunlap Observatory (DDO) catalog, catalogsType, galaxies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogsType Context triple: [David Dunlap Observatory (DDO) catalog, catalogsType, galaxies]
-
A.
catalogueType
chosen
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
B.
catalogueFor
Indicates that one entity serves as a catalog or organized listing that describes, indexes, or inventories another entity.
-
C.
catalogueSystem
Indicates a relationship where one entity serves as or belongs to a cataloging system that organizes, indexes, or classifies other entities.
-
D.
subjectOfCatalog
Indicates that something is the primary focus or entry described within a catalog or cataloging record.
-
E.
catalog
Indicates the action of systematically listing, organizing, or recording items or information into a structured collection or database.
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17907d7288190bb53f76974f95cef |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:17 p.m.