Triple
T30598453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Reliant |
E778845
|
entity |
| Predicate | hasRegistryPrefix |
P202559
|
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: [USS Reliant, hasRegistryPrefix, NCC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegistryPrefix Context triple: [USS Reliant, hasRegistryPrefix, NCC]
-
A.
hasPrefix
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
B.
hasOriginalPrefix
Indicates that an entity retains or is associated with its initial or primary prefix from which later forms or variants are derived.
-
C.
hasPrincipalRegistryIn
Indicates that an entity’s primary or main official registration is located in a specified registry or jurisdiction.
-
D.
hasAbbreviationPrefix
Indicates that one term’s abbreviation begins with the same initial sequence of characters as another specified string or term.
-
E.
hasRegistryView
Indicates that an entity has permission or capability to access and view a particular registry or registry-related information.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0091ad8b8c8190b0f00a3358e59bc1 |
completed | May 10, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_6a008f2813ec81909a54c2dfa5c75dc7 |
completed | May 10, 2026, 1:59 p.m. |
| PDg | Predicate description generation | batch_6a0091ac9ff08190b635eac6aa3f6128 |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 29, 2026, 8:25 p.m.