Triple
T28060180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4th Battalion, 506th Infantry Regiment |
E709081
|
entity |
| Predicate | mottoOfRegiment |
P163438
|
FINISHED |
| Object | Currahee |
—
|
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: Currahee | Statement: [4th Battalion, 506th Infantry Regiment, mottoOfRegiment, Currahee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoOfRegiment Context triple: [4th Battalion, 506th Infantry Regiment, mottoOfRegiment, Currahee]
-
A.
regimentalMottoTranslation
Indicates the translated wording or meaning of a regiment’s official motto in another language.
-
B.
parentRegimentMotto
Indicates that one regiment’s motto is derived from, associated with, or officially linked to the motto of its parent regiment.
-
C.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
D.
honorificMotto
Indicates that one entity serves as an honorific motto or formal laudatory phrase associated with another entity.
-
E.
mottoOfBranch
Indicates that a particular motto is officially associated with and represents a specific branch of an organization or institution.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6401689808190874b7d29a32d534f |
completed | May 2, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f637120c008190b2b5adf46f022e48 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f637cad530819086cad3a5ec156013 |
completed | May 2, 2026, 5:43 p.m. |
Created at: April 27, 2026, 8:39 p.m.