Triple
T18443875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 6726 |
E450603
|
entity |
| Predicate | discoveredInCatalogue |
P131632
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [NGC 6726, discoveredInCatalogue, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredInCatalogue Context triple: [NGC 6726, discoveredInCatalogue, 19th century]
-
A.
usedInCatalogue
Indicates that something is included or referenced as an entry within a catalogue.
-
B.
hasDiscoveryCatalogue
Indicates that an entity is associated with a specific discovery catalogue in which it is recorded or listed.
-
C.
hasDiscoveryCatalog
Indicates that an entity is associated with a specific discovery catalog in which it is recorded or listed.
-
D.
discoveredAsPartOf
Indicates that something was found, identified, or revealed in the course of a larger activity, process, or investigation of which it formed a component.
-
E.
catalogueFor
Indicates that one entity serves as a catalog or organized listing that describes, indexes, or inventories another entity.
- F. None of above. chosen
Provenance (4 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c142abc8190b4f6f938acdc413d |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:30 a.m.