Triple
T26007878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All American patch of the 82nd Airborne Division |
E646809
|
entity |
| Predicate | featuresLetters |
P2003
|
FINISHED |
| Object | AA |
—
|
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: AA | Statement: [All American patch of the 82nd Airborne Division, featuresLetters, AA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresLetters Context triple: [All American patch of the 82nd Airborne Division, featuresLetters, AA]
-
A.
featuresText
chosen
Indicates that an entity includes or presents a specific piece of text as one of its characteristics or contents.
-
B.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
C.
featuresSign
Indicates that an entity includes, displays, or incorporates a particular sign as part of its appearance, content, or design.
-
D.
spanFeature
Indicates a relationship where a feature or characteristic extends across or covers a specified span or interval.
-
E.
featuresLeader
Indicates that one entity includes, presents, or highlights another entity in the role of a leader.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 22, 2026, 9:01 a.m.