Triple
T7424993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Raid offense |
E171345
|
entity |
| Predicate | usesFormationType |
P23125
|
FINISHED |
| Object | spread formation |
—
|
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: spread formation | Statement: [Air Raid offense, usesFormationType, spread formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFormationType Context triple: [Air Raid offense, usesFormationType, spread formation]
-
A.
containsFormation
Indicates that one entity spatially or structurally includes or encloses a formation as part of its extent or composition.
-
B.
formationType
chosen
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
-
C.
onFormation
Indicates that one entity is located on or attached to the surface of a formation (such as a geological or structural feature).
-
D.
usesForm
Indicates that one entity employs, applies, or operates through a particular form, format, or structured representation of something.
-
E.
supportedFormation
Indicates that one entity provided assistance, resources, or conditions that enabled the creation or establishment of another entity or structure.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f302b33481908eae877970f2bbdf |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.