Triple
T38038404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Wyoming |
E949412
|
entity |
| Predicate | hasPartRemoved |
P124287
|
FINISHED |
| Object | main armament |
—
|
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: main armament | Statement: [USS Wyoming, hasPartRemoved, main armament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartRemoved Context triple: [USS Wyoming, hasPartRemoved, main armament]
-
A.
removalPartOf
chosen
Indicates that one entity is a component or portion that has been taken away or extracted from another entity.
-
B.
hasPartUsed
Indicates that an entity utilizes another entity as a component or constituent part in its structure, function, or operation.
-
C.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
D.
hasStructureRemnant
Indicates that an entity contains or includes a remaining part or leftover portion of a former structure.
-
E.
destroyedPart
Indicates that one entity has caused damage to or ruined a portion or component of another entity.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00717f539c8190b70dd0e72c6f7d24 |
completed | May 10, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_6a00710278fc81908889afdcf459ff01 |
completed | May 10, 2026, 11:50 a.m. |
Created at: May 3, 2026, 4:20 p.m.