Triple
T19831199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC |
E476463
|
entity |
| Predicate | catalogNumberFormat |
P78161
|
FINISHED |
| Object | NGC followed by an integer index |
—
|
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: NGC followed by an integer index | Statement: [NGC, catalogNumberFormat, NGC followed by an integer index]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogNumberFormat Context triple: [NGC, catalogNumberFormat, NGC followed by an integer index]
-
A.
identificationNumberFormat
chosen
Indicates the specific structural pattern or rules that an identification number must follow.
-
B.
categoryNumbering
Indicates that items within a category are assigned an ordered or structured numbering scheme that defines their position or sequence in that category.
-
C.
catalogNumberDDO
Indicates the identifier or catalog number assigned to an item within the DDO cataloging or documentation system.
-
D.
codenameFormat
Indicates that an entity’s codename follows a specific prescribed format or pattern.
-
E.
serialNumber
Indicates a unique identifying code assigned to an individual item or instance within a series or batch.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656ce68b48190aa25b29d0b6ea021 |
completed | April 20, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.