Triple
T1519924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States home front during World War II |
E32202
|
entity |
| Predicate | homeLifeChange |
P3562
|
FINISHED |
| Object | food rationing |
—
|
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: food rationing | Statement: [United States home front during World War II, homeLifeChange, food rationing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeLifeChange Context triple: [United States home front during World War II, homeLifeChange, food rationing]
-
A.
lifestyle
chosen
Indicates that an entity’s way of living or habitual behaviors are associated with, influence, or characterize another entity or outcome.
-
B.
living
Indicates that an entity is alive or currently exists in a living state.
-
C.
homeTo
Indicates that a place serves as the primary location, residence, or habitat for a person, group, or thing.
-
D.
householdPractice
Indicates a relationship where an entity engages in or carries out a particular practice, behavior, or routine within the context of a household.
-
E.
lifeCycle
Indicates the sequence of stages or phases an entity passes through from its beginning, through development and use, to its end or termination.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93d4756888190bf3872154de11539 |
completed | March 5, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69a907ac7ea081908dd95bb5cc3b9847 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.