Triple
T31762677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 369th Infantry Regiment |
E810722
|
entity |
| Predicate | frontLineServiceDuration |
P173778
|
FINISHED |
| Object | over 180 days in combat |
—
|
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: over 180 days in combat | Statement: [369th Infantry Regiment, frontLineServiceDuration, over 180 days in combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontLineServiceDuration Context triple: [369th Infantry Regiment, frontLineServiceDuration, over 180 days in combat]
-
A.
frontLineService
Indicates that an entity provides direct, first-contact service or support to customers, clients, or the public.
-
B.
frontLineLength
Indicates the total measured extent of the front line where opposing forces or boundaries directly face each other.
-
C.
frontLineDuring
Indicates that an entity is positioned at or serves on the front line during a specified time or event.
-
D.
frontlineService
Indicates that an entity provides direct, first-point-of-contact service or support to end users or customers.
-
E.
frontLine
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: April 30, 2026, 11:31 p.m.