Triple
T7987100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remember WENN |
E185707
|
entity |
| Predicate | hasTimeSettingContext |
P79788
|
FINISHED |
| Object | World War II era |
—
|
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: World War II era | Statement: [Remember WENN, hasTimeSettingContext, World War II era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeSettingContext Context triple: [Remember WENN, hasTimeSettingContext, World War II era]
-
A.
hasTimeOptions
Indicates that an entity is associated with one or more selectable time choices or configurations.
-
B.
hasTimeStart
Indicates that an event, process, or state begins at a specific point in time.
-
C.
hasTimingCapability
Indicates that an entity possesses the ability to measure, control, or manage timing-related aspects of an operation or process.
-
D.
hasTimeIndication
chosen
Indicates that something includes, specifies, or is associated with a particular time-related indication (such as a timestamp, time period, or temporal marker).
-
E.
hasTimeOffset
Indicates that one temporal value is shifted or displaced from another by a specified amount of time.
- 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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c4d11b08190aa13afb17155462c |
completed | March 31, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:15 p.m.