Triple
T38148765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Independence |
E952692
|
entity |
| Predicate | armedFor |
P40410
|
FINISHED |
| Object | ship-to-ship combat |
—
|
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: ship-to-ship combat | Statement: [USS Independence, armedFor, ship-to-ship combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedFor Context triple: [USS Independence, armedFor, ship-to-ship combat]
-
A.
armed
Indicates that an entity is equipped with or carrying a weapon or weapons.
-
B.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
C.
armedAgainst
Indicates that one entity is equipped with weapons or defensive capabilities specifically in preparation for potential conflict with another entity.
-
D.
equippedFor
chosen
Indicates that one entity is suitably provided with the necessary tools, features, or capabilities to perform a particular function or handle a specific situation for another entity or purpose.
-
E.
armamentFlexible
Indicates that an entity’s armament or weapon configuration can be adjusted, reconfigured, or adapted to different setups or roles.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.