Triple
T34600684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 118th Field Artillery Regiment |
E888451
|
entity |
| Predicate | isHistoricUnit |
P4238
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [118th Field Artillery Regiment, isHistoricUnit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricUnit Context triple: [118th Field Artillery Regiment, isHistoricUnit, true]
-
A.
isHistoricFor
Indicates that something has historical significance, relevance, or impact specifically in relation to a given entity or context.
-
B.
isHistoric
chosen
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
C.
isHistoricSee
Indicates that one entity serves or functioned as a historically significant viewing point or place from which another entity is or was seen.
-
D.
isHistoricRegionFor
Indicates that one entity serves as a historically recognized region associated with, or significant to, another entity.
-
E.
isInHistoricRegister
Indicates that an entity has been officially listed or recorded in a recognized historic register or registry.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:03 a.m.