Triple
T13015378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Royds |
E322536
|
entity |
| Predicate | HSMNumber |
P107835
|
FINISHED |
| Object | HSM 15 |
—
|
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: HSM 15 | Statement: [Cape Royds, HSMNumber, HSM 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HSMNumber Context triple: [Cape Royds, HSMNumber, HSM 15]
-
A.
SSNumber
Indicates that an entity has a specific Social Security Number assigned to it.
-
B.
MMSINumber
Indicates a relationship where a mobile subscriber is associated with a specific Mobile Station International ISDN Number (MSISDN) used to identify their phone line in a mobile network.
-
C.
HSTServicingNumber
Indicates the specific servicing mission number associated with work performed on the Hubble Space Telescope.
-
D.
imoNumber
Indicates that an entity is associated with a specific International Maritime Organization (IMO) identification number used to uniquely identify ships and certain maritime structures.
-
E.
symbolNumber
Indicates a relationship where a specific numerical identifier is assigned to or associated with a particular symbol.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecd04748190ade2530ee5db35fe |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e74283c819082e69ac3554fa7d8 |
completed | April 10, 2026, 10:49 p.m. |
Created at: April 9, 2026, 8:50 p.m.