Triple
T6031402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Draper Catalogue |
E134310
|
entity |
| Predicate | hasIdentifierFormat |
P23479
|
FINISHED |
| Object | HD number |
—
|
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: HD number | Statement: [Henry Draper Catalogue, hasIdentifierFormat, HD number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIdentifierFormat Context triple: [Henry Draper Catalogue, hasIdentifierFormat, HD number]
-
A.
hasIdentifierSystem
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
B.
hasFormatElement
chosen
Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
-
C.
haveIdentifier
Indicates that an entity is associated with a specific identifier used to uniquely reference or distinguish it.
-
D.
hasMatchFormat
Indicates that something (such as a game, event, or competition) is conducted according to a specified match format or structure.
-
E.
hasFormatCurrent
Indicates that an entity is available or expressed in the currently used or most up-to-date format.
- 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056af89e881909652957f94317684 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.