Triple
T21927748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 82nd Illinois Infantry Regiment |
E541484
|
entity |
| Predicate | sizeType |
P146598
|
FINISHED |
| Object | regiment |
—
|
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: regiment | Statement: [82nd Illinois Infantry Regiment, sizeType, regiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sizeType Context triple: [82nd Illinois Infantry Regiment, sizeType, regiment]
-
A.
sizeDefinedBy
Indicates that the size or magnitude of one entity is determined, constrained, or specified by another entity.
-
B.
sizeStatus
Indicates the relative size condition or classification of one entity in relation to another or to a defined standard.
-
C.
sizeDescription
Indicates a relationship where one entity provides descriptive information about the size or scale of another entity.
-
D.
bodySize
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
E.
sizeCategory
Indicates the relative size classification assigned to an entity compared to others (e.g., small, medium, large).
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e6fb6991948190a428c3c3bfd1c3b8 |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 7:46 p.m.