Triple
T7425004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Raid offense |
E171345
|
entity |
| Predicate | playCallingStyle |
P76902
|
FINISHED |
| Object | pass-heavy |
—
|
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: pass-heavy | Statement: [Air Raid offense, playCallingStyle, pass-heavy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playCallingStyle Context triple: [Air Raid offense, playCallingStyle, pass-heavy]
-
A.
callingStyle
Indicates the manner or convention by which one entity initiates or performs a call or invocation on another entity.
-
B.
callType
Indicates the category or nature of a call (such as its purpose, direction, or handling), distinguishing one kind of call from another.
-
C.
hasCallInNumber
Indicates that an entity has an associated telephone number designated for receiving incoming calls.
-
D.
ringingMethod
Indicates that one entity uses or is associated with a specific method or pattern for ringing (such as in bell-ringing or similar signaling activities).
-
E.
callingPoint
Indicates that one entity serves as a stop, station, or intermediate point that another entity (such as a route, journey, or service) calls at or passes through.
- 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_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. |
| PDg | Predicate description generation | batch_69c6f1ee5ab8819091082324f2dc3b8c |
completed | March 27, 2026, 9:09 p.m. |
Created at: March 27, 2026, 3:12 p.m.