Triple
T19407766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 40th Infantry Regiment |
E485506
|
entity |
| Predicate | racePolicyContext |
P23600
|
FINISHED |
| Object | segregated unit |
—
|
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: segregated unit | Statement: [40th Infantry Regiment, racePolicyContext, segregated unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racePolicyContext Context triple: [40th Infantry Regiment, racePolicyContext, segregated unit]
-
A.
racePolicy
chosen
Indicates that an entity has established rules, practices, or guidelines governing how races or competitive events are conducted or managed.
-
B.
raceContext
Indicates the situational or environmental circumstances under which a race or competitive event takes place.
-
C.
policyContext
Indicates the situational or regulatory framework within which a policy is defined, interpreted, or applied.
-
D.
ordinationPolicy
Indicates the rules or criteria governing how entities are ordered, ranked, or arranged relative to one another.
-
E.
closurePolicyContext
Indicates the policy or set of rules that governs how and under what conditions a process, case, or entity is brought to closure.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6257bad0c819088dd7729b6a36a94 |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:36 p.m.