Triple
T2202234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Task Force One |
E50515
|
entity |
| Predicate | testObjective |
P36954
|
FINISHED |
| Object | study effects of nuclear explosions on naval vessels |
—
|
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: study effects of nuclear explosions on naval vessels | Statement: [Joint Task Force One, testObjective, study effects of nuclear explosions on naval vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testObjective Context triple: [Joint Task Force One, testObjective, study effects of nuclear explosions on naval vessels]
-
A.
tests
Indicates that one entity examines, evaluates, or checks another entity or condition to determine its properties, performance, or correctness.
-
B.
controlObjective
Indicates that one entity defines or specifies a control goal or target that another entity is intended to achieve or satisfy.
-
C.
testType
Indicates the specific category or kind of test associated with an entity or event.
-
D.
testsIn
Indicates that one entity conducts or performs tests within, on, or using another entity.
-
E.
appliedTest
Indicates that a test has been administered or carried out on a particular subject or object.
- F. None of above. chosen
Provenance (4 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfa33f0881908403604eafb73ecf |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf35c994819088a093c412931de4 |
completed | March 7, 2026, 6:01 a.m. |
Created at: March 4, 2026, 7:46 p.m.