Triple
T34147348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS America (CV-66) |
E875897
|
entity |
| Predicate | sinkingPurpose |
P100921
|
FINISHED |
| Object | weapons effects testing |
—
|
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: weapons effects testing | Statement: [USS America (CV-66), sinkingPurpose, weapons effects testing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sinkingPurpose Context triple: [USS America (CV-66), sinkingPurpose, weapons effects testing]
-
A.
sunkBy
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
-
B.
placeOfSinking
Indicates the location where an object or entity sank or was submerged.
-
C.
sunkDuring
Indicates that one entity was sunk in the course of, or as a result of, the event or time period represented by another entity.
-
D.
reasonForSinking
chosen
Indicates the cause or circumstance that led to something sinking.
-
E.
sankWhile
Indicates that one entity moved downward below a surface or level at the same time that another specified event or action was occurring.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.