Triple
T22812690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa in the Civil War |
E565022
|
entity |
| Predicate | homeFrontActivity |
P106898
|
FINISHED |
| Object | recruitment of volunteers |
—
|
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: recruitment of volunteers | Statement: [Iowa in the Civil War, homeFrontActivity, recruitment of volunteers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeFrontActivity Context triple: [Iowa in the Civil War, homeFrontActivity, recruitment of volunteers]
-
A.
homeFront
chosen
Indicates a relationship where an entity is associated with the domestic sphere or civilian side of a conflict, typically supporting war efforts away from the battlefield.
-
B.
homeFeature
Indicates that a home possesses or includes a particular feature or amenity.
-
C.
homeFunction
Indicates that something serves as the primary place where an entity lives, resides, or is based.
-
D.
homeTo
Indicates that a place serves as the primary location, residence, or habitat for a person, group, or thing.
-
E.
homeMatchActivity
Indicates an activity or event that takes place during a match played at the home venue of a team or participant.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d61c6f081908d3911710b3aff51 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:32 p.m.