Triple

T22635083
Position Surface form Disambiguated ID Type / Status
Subject 75th Ranger Regiment E558658 entity
Predicate abbreviation P43 FINISHED
Object 75th RR 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: 75th RR | Statement: [75th Ranger Regiment, abbreviation, 75th RR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 75th RR
Context triple: [75th Ranger Regiment, abbreviation, 75th RR]
  • A. 75th RR chosen
    The 75th RR is an elite U.S. Army special operations light infantry unit known for rapid deployment, direct action raids, and airborne operations.
  • B. 75 RR
    75 RR is the commonly used abbreviation for the U.S. Army’s elite 75th Ranger Regiment, a premier airborne light infantry special operations unit.
  • C. R55
    R55 is a regional road in South Africa that runs through Gauteng, connecting areas such as Midrand with surrounding suburbs and major routes.
  • D. R5 Paoli
    R5 Paoli was the former designation for a commuter rail service segment on SEPTA’s Paoli/Thorndale Line in the Philadelphia area.
  • E. S75
    S75 is a line of the Berlin S-Bahn urban rail network serving routes within the Berlin metropolitan area.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245467d9881908d6985bd0db7a1f1 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1700d492081909bab8d9dbb1faef2 completed April 29, 2026, 2:42 a.m.
Created at: April 17, 2026, 3:03 p.m.