Triple
T21927731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 82nd Illinois Infantry Regiment |
E541484
|
entity |
| Predicate | languageSpokenInRanks |
P741
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [82nd Illinois Infantry Regiment, languageSpokenInRanks, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageSpokenInRanks Context triple: [82nd Illinois Infantry Regiment, languageSpokenInRanks, German]
-
A.
rankedByNumberOfNativeSpeakers
Indicates that entities are ordered or classified according to how many native speakers they have.
-
B.
languagesSpoken
chosen
Indicates that an entity is able to communicate using one or more specified languages.
-
C.
languageGroupSpoken
Indicates that a particular language group is spoken or used for communication by an entity.
-
D.
includesLanguagesSpokenBy
Indicates that one entity contains or covers the set of languages spoken by another entity.
-
E.
nationalLanguageSpoken
Indicates that a particular language is officially recognized and commonly used as a national language within a given country or region.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123fc188481909c74fd5f1bd52258 |
completed | April 28, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:46 p.m.