Triple
T831024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audie Murphy |
E17964
|
entity |
| Predicate | reasonForRejection |
P10714
|
FINISHED |
| Object | underweight and underage |
—
|
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: underweight and underage | Statement: [Audie Murphy, reasonForRejection, underweight and underage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForRejection Context triple: [Audie Murphy, reasonForRejection, underweight and underage]
-
A.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
-
B.
reasonForDisqualification
chosen
Indicates the specific cause or justification for which an entity was deemed ineligible or disqualified from consideration or participation.
-
C.
reasonForReoffer
Indicates the reason or justification for presenting something again after it was previously offered.
-
D.
cancellationReason
Indicates the reason or cause for which a previously scheduled or planned action, event, or agreement was canceled.
-
E.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb4be948190ae757df85bdc40e4 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7b3d2481909199f7c9f305bdfe |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.