Triple
T28000610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meaning in History |
E707138
|
entity |
| Predicate | tracesOriginOf |
P11414
|
FINISHED |
| Object | modern historical consciousness |
—
|
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: modern historical consciousness | Statement: [Meaning in History, tracesOriginOf, modern historical consciousness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tracesOriginOf Context triple: [Meaning in History, tracesOriginOf, modern historical consciousness]
-
A.
traceOf
Indicates that one entity is a remaining sign, mark, or residual evidence of the presence, existence, or action of another entity.
-
B.
tracesTo
chosen
Indicates a relationship where one item can be followed or linked back as the origin, source, or cause of another.
-
C.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
D.
describesOriginOf
Indicates that one entity specifies or explains the source, provenance, or origin of another entity.
-
E.
depictsOriginOf
Indicates that one entity visually represents or illustrates the source, beginning, or point of origin of 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63baed07c8190a48e5911fc8b270b |
completed | May 2, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:56 p.m.