Triple
T21887604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Arrows |
E540446
|
entity |
| Predicate | loopManeuvers |
P138443
|
FINISHED |
| Object | synchronized loops |
—
|
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: synchronized loops | Statement: [Black Arrows, loopManeuvers, synchronized loops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loopManeuvers Context triple: [Black Arrows, loopManeuvers, synchronized loops]
-
A.
maneuverType
chosen
Indicates the specific kind or category of maneuver being performed or described in a given context.
-
B.
notableManeuver
Indicates that an entity is recognized for performing a specific maneuver, action, or tactical move that is considered notable or significant.
-
C.
rotatesAmong
Indicates that an entity takes turns occupying or performing a role, position, or function in sequence with other entities.
-
D.
movementCycle
Indicates a recurring pattern or sequence of movements that an entity performs over a period of time.
-
E.
turns
Indicates a change in orientation, direction, or state initiated by one entity affecting itself or 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ee5f1c8190b8c6c431039eb8c9 |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.