Triple
T37104904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IC 4617 |
E918814
|
entity |
| Predicate | discoveryCatalog |
P104430
|
FINISHED |
| Object | Second Index Catalogue (IC II) |
—
|
NE NERFINISHED |
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: Second Index Catalogue (IC II) | Statement: [IC 4617, discoveryCatalog, Second Index Catalogue (IC II)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryCatalog Context triple: [IC 4617, discoveryCatalog, Second Index Catalogue (IC II)]
-
A.
discoveryCataloger
Indicates that an entity is responsible for cataloging or recording discoveries made by another entity.
-
B.
discoveredInCatalogue
Indicates that an entity was identified or first recognized through information found in a specific catalogue.
-
C.
hasDiscoveryCatalog
Indicates that an entity is associated with a specific discovery catalog in which it is recorded or listed.
-
D.
hasDiscoveryCatalogue
chosen
Indicates that an entity is associated with a specific discovery catalogue in which it is recorded or listed.
-
E.
discovery
Indicates the event or process by which one entity finds, uncovers, or identifies something previously unknown or unrecognized.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:14 p.m.