Triple
T19210333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Need for Roots |
E480339
|
entity |
| Predicate | addressesContext |
P12095
|
FINISHED |
| Object | aftermath of modern upheavals |
—
|
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: aftermath of modern upheavals | Statement: [The Need for Roots, addressesContext, aftermath of modern upheavals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressesContext Context triple: [The Need for Roots, addressesContext, aftermath of modern upheavals]
-
A.
addressContext
chosen
Indicates the situational or conversational setting in which an address (such as a location, contact, or reference) is used or interpreted.
-
B.
addresses
Indicates that one entity directs speech, communication, or written correspondence specifically toward another entity.
-
C.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
D.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
-
E.
addressesPosition
Indicates that one entity communicates with, responds to, or deals with the role, status, or job position held by another entity.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f9a0d1248190953e36e44f0cafdd |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:21 p.m.