Triple
T30617989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Forces Assessment and Selection |
E779364
|
entity |
| Predicate | targetUnitNickname |
P88554
|
FINISHED |
| Object | Green Berets |
—
|
NE NERFINISHED |
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: Green Berets | Statement: [Special Forces Assessment and Selection, targetUnitNickname, Green Berets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetUnitNickname Context triple: [Special Forces Assessment and Selection, targetUnitNickname, Green Berets]
-
A.
targetUnit
Indicates that one entity serves as the specific unit or object that another entity is directed at, operates on, or is intended to affect.
-
B.
nicknameOfUnitUsing
chosen
Indicates that one unit serves as an informal or alternative name (nickname) for another unit that is being used.
-
C.
nicknameOfParentUnit
Indicates that one unit serves as an informal or alternative name (nickname) for its parent unit.
-
D.
militaryUnitName
Indicates the specific official name assigned to a military unit in the context of a broader relationship or record.
-
E.
notableTeamUnit
Indicates that an entity is a significant or distinguished member unit (such as a player or component) of a particular team.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: April 29, 2026, 8:26 p.m.