Triple
T8460997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Total Strategy security doctrine |
E200037
|
entity |
| Predicate | basedOnConceptOf |
P7125
|
FINISHED |
| Object | total onslaught |
—
|
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: total onslaught | Statement: [Total Strategy security doctrine, basedOnConceptOf, total onslaught]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnConceptOf Context triple: [Total Strategy security doctrine, basedOnConceptOf, total onslaught]
-
A.
basingConcept
Indicates that one concept serves as the foundational basis or underlying rationale for another concept.
-
B.
basedOnSeriesConceptBy
Indicates that something is derived from or created using a series concept developed by a specified source.
-
C.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
D.
isBasedOn
chosen
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
E.
areBasedOn
Indicates that one entity is founded, derived, or developed from the principles, content, or structure of 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4a0ff4c8190b17bbd33db632cea |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.