Triple
T7424996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Raid offense |
E171345
|
entity |
| Predicate | typicalPersonnel |
P2776
|
FINISHED |
| Object | multiple wide receivers |
—
|
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: multiple wide receivers | Statement: [Air Raid offense, typicalPersonnel, multiple wide receivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPersonnel Context triple: [Air Raid offense, typicalPersonnel, multiple wide receivers]
-
A.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
B.
typicalMembers
chosen
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
C.
personnel
Indicates that an entity serves as staff or workforce associated with another entity, such as an organization, project, or facility.
-
D.
personnelComposition
Indicates the makeup or distribution of people or roles within a group, organization, or unit.
-
E.
peakPersonnel
Indicates the maximum number of personnel involved or present at any point during a specified period or activity.
- 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.