Triple
T25225687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCC-74656 |
E632079
|
entity |
| Predicate | registryFormat |
P158302
|
FINISHED |
| Object | NCC-##### |
—
|
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: NCC-##### | Statement: [NCC-74656, registryFormat, NCC-#####]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registryFormat Context triple: [NCC-74656, registryFormat, NCC-#####]
-
A.
distributedFormat
Indicates that an entity is made available or disseminated in a particular format or medium.
-
B.
registryType
Indicates the specific category or classification of a registry that an entity is associated with or recorded in.
-
C.
storageFormat
Indicates the specific way in which data or content is physically or logically organized, encoded, and stored.
-
D.
registryName
Indicates that an entity is identified or labeled by a specific name within a registry or registration system.
-
E.
containerFormats
Indicates that one entity serves as a container or packaging format used to hold, encapsulate, or structure the contents of 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47cc342948190acae4979648659bd |
completed | May 1, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f465699c9c8190ac7b4b32b782550c |
completed | May 1, 2026, 8:33 a.m. |
Created at: April 21, 2026, 1:03 p.m.