Triple
T6341973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10th U.S. Cavalry Regiment |
E142648
|
entity |
| Predicate | hadOfficerCorps |
P64315
|
FINISHED |
| Object | White officers |
—
|
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: White officers | Statement: [10th U.S. Cavalry Regiment, hadOfficerCorps, White officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadOfficerCorps Context triple: [10th U.S. Cavalry Regiment, hadOfficerCorps, White officers]
-
A.
officerCorps
chosen
Indicates that an entity belongs to, is part of, or is associated with a group or body of officers within an organization or institution.
-
B.
hasCadetBranch
Indicates that one lineage, family, or house is a junior or offshoot branch derived from another main or senior line.
-
C.
hasCorpsOfCadets
Indicates that an institution maintains an organized corps of cadets as part of its structure or programs.
-
D.
isMilitaryOfficer
Indicates that the subject holds an official position as an officer within a military organization.
-
E.
hasArtilleryCorps
Indicates that an entity possesses, includes, or is associated with an artillery corps as part of its military forces.
- 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0674445748190bce2d638048be77c |
completed | March 22, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.