Triple
T6513922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24th U.S. Infantry Regiment |
E148205
|
entity |
| Predicate | servicePeriodStart |
P61845
|
FINISHED |
| Object | 1869 |
—
|
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: 1869 | Statement: [24th U.S. Infantry Regiment, servicePeriodStart, 1869]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servicePeriodStart Context triple: [24th U.S. Infantry Regiment, servicePeriodStart, 1869]
-
A.
serviceEntryPeriod
Indicates the span of time during which a service is active, valid, or in effect for the related entities.
-
B.
serviceEntryDate
chosen
Indicates the date on which a service or duty officially began or was first entered into the record.
-
C.
grantPeriodStart
Indicates the date or time at which a grant’s active period or coverage begins.
-
D.
serviceOpenedBetween
Indicates that a service has been initiated or made available during the time interval between two specified points or events.
-
E.
usePeriodStart
Indicates that an entity begins to be used or becomes active starting from a specified time period.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f3db330819092503af4fb0649ea |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.