Triple
T33988324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IX-300 |
E871471
|
entity |
| Predicate | roleInTests |
P22824
|
FINISHED |
| Object | target ship for atomic bomb detonations |
—
|
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: target ship for atomic bomb detonations | Statement: [IX-300, roleInTests, target ship for atomic bomb detonations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTests Context triple: [IX-300, roleInTests, target ship for atomic bomb detonations]
-
A.
testRole
chosen
Indicates that an entity is assigned or associated with a specific role used for testing or validation purposes.
-
B.
roleInTheWay
Indicates that one entity is obstructing, hindering, or otherwise blocking another entity’s progress, action, or intended path.
-
C.
roleInSpecification
Indicates that an entity participates in a specification with a particular role or function within that specification.
-
D.
roleInIntegration
Indicates the specific function or responsibility an entity has within a combined or coordinated system, process, or integration.
-
E.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00b34364448190b8c9948d5a24d845 |
completed | May 10, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_6a00b2e4f13c819081bac7d763c414ad |
completed | May 10, 2026, 4:31 p.m. |
Created at: May 1, 2026, 1:50 a.m.