Triple
T27522994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Oral History Office |
E694759
|
entity |
| Predicate | documentedTheme |
P133933
|
FINISHED |
| Object | community history |
—
|
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: community history | Statement: [Regional Oral History Office, documentedTheme, community history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentedTheme Context triple: [Regional Oral History Office, documentedTheme, community history]
-
A.
documentsTheme
chosen
Indicates that a document records, discusses, or centers around a particular theme or subject.
-
B.
notableTheme
Indicates that a particular theme is prominently featured in, or strongly associated with, an entity such as a work, event, or body of content.
-
C.
dataTheme
Indicates the primary subject area or thematic category that the associated data pertains to.
-
D.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
E.
featuresThemeBy
Indicates that something (such as a work, event, or product) prominently includes or centers around a particular theme created or defined by a specified source or 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 1:22 p.m.