Triple
T13278553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Vega |
E316255
|
entity |
| Predicate | hasReinforcedHull |
P92616
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SS Vega, hasReinforcedHull, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReinforcedHull Context triple: [SS Vega, hasReinforcedHull, true]
-
A.
isFortifiedWith
Indicates that one entity has been strengthened, enriched, or supplemented by the addition of another entity.
-
B.
enhancedArmament
Indicates that an entity’s weaponry or combat equipment has been upgraded, augmented, or otherwise improved beyond its standard configuration.
-
C.
hasImprovedArmorOverT72
Indicates that an entity possesses armor that is superior in protection or performance compared to that of the T-72 tank.
-
D.
hasExplosiveReactiveArmor
Indicates that the subject is equipped with explosive reactive armor as a protective defensive feature.
-
E.
armored
chosen
Indicates that an entity is protected by armor or a defensive covering against damage or attack.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.