Triple
T7194089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia-class submarine |
E167765
|
entity |
| Predicate | blockVariant |
P57059
|
FINISHED |
| Object | Block I |
—
|
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: Block I | Statement: [Virginia-class submarine, blockVariant, Block I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockVariant Context triple: [Virginia-class submarine, blockVariant, Block I]
-
A.
blockType
chosen
Indicates that one entity is classified as a specific type or category of block in relation to another entity.
-
B.
programmingBlock
Indicates a relationship where one entity is a defined segment or unit of programming logic (such as a code block or script section) associated with or contained within another entity.
-
C.
block
Indicates preventing or obstructing another entity’s action, movement, or access.
-
D.
brickButtons
Indicates that one entity presses, activates, or otherwise operates the buttons associated with another entity.
-
E.
scriptVariantOf
Indicates that one script is a variant or alternative form of another script, typically differing in style, region, or historical development while remaining closely related.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e9050164819081fd6a11d10f9833 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.