Triple
T33701367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brumley |
E863462
|
entity |
| Predicate | reflectsHistoricalContext |
P1409
|
FINISHED |
| Object | pre-World War I Britain |
—
|
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: pre-World War I Britain | Statement: [Brumley, reflectsHistoricalContext, pre-World War I Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsHistoricalContext Context triple: [Brumley, reflectsHistoricalContext, pre-World War I Britain]
-
A.
hasHistoricalContext
chosen
Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
-
B.
hasHistoricalContextDisplays
Indicates that something presents or showcases information within a broader historical background or setting.
-
C.
shareHistoricalContextAs
Indicates that two or more entities are associated with or understood within the same historical background, period, or circumstances.
-
D.
reflectsHistoricalDevelopmentOf
Indicates that something embodies, illustrates, or reveals the way another thing has changed or evolved over time in its historical development.
-
E.
historicallyEncompassed
Indicates that one entity previously included, covered, or contained another entity within its scope, extent, or boundaries during a past historical period.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:43 a.m.