Triple
T14444099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFCCA |
E358158
|
entity |
| Predicate | reviewsConvictionsOf |
P114299
|
FINISHED |
| Object | members of the United States Air Force |
—
|
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: members of the United States Air Force | Statement: [AFCCA, reviewsConvictionsOf, members of the United States Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reviewsConvictionsOf Context triple: [AFCCA, reviewsConvictionsOf, members of the United States Air Force]
-
A.
convictedBy
Indicates that an authority, typically a court or judge, has formally found an entity guilty of a crime or offense.
-
B.
convictedOf
Indicates that a person or entity has been found guilty of committing a specified offense or crime through a formal legal process.
-
C.
numberOfConvictions
Indicates the count of times an entity has been formally found guilty of an offense.
-
D.
reasonForConviction
Indicates the specific offense or legal basis for which an individual was found guilty or convicted.
-
E.
convictedIndividual
Indicates that an individual has been found guilty of a crime or offense through a formal legal process and has received a conviction.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de915e76f481909fe9462f964b5b1c |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:19 a.m.