Triple
T12209391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Bravo |
E290915
|
entity |
| Predicate | testSeriesNumber |
P61667
|
FINISHED |
| Object | first test in Operation Castle series |
—
|
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: first test in Operation Castle series | Statement: [Castle Bravo, testSeriesNumber, first test in Operation Castle series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testSeriesNumber Context triple: [Castle Bravo, testSeriesNumber, first test in Operation Castle series]
-
A.
testSeriesRole
Indicates the specific role or function an entity has within a test series or sequence of tests.
-
B.
hasSeriesNumber
chosen
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
C.
numberOfSeries
Indicates the total count of distinct series associated with or contained within a given entity.
-
D.
testSeriesPurpose
Indicates that a test series is conducted with the specific purpose or objective of achieving a particular outcome or goal.
-
E.
seriesOf
Indicates that one entity is a sequence or ordered set of related items, events, or parts that collectively form or belong to 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.