Triple
T1507006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black May 1943 |
E33923
|
entity |
| Predicate | hasPointInTime |
P22881
|
FINISHED |
| Object | May 1943 |
—
|
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: May 1943 | Statement: [Black May 1943, hasPointInTime, May 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPointInTime Context triple: [Black May 1943, hasPointInTime, May 1943]
-
A.
supportsTimestamps
Indicates that the subject is capable of handling, storing, or recognizing timestamp information associated with relevant data or events.
-
B.
hasLongTermDatasetSince
Indicates that an entity has maintained or used a particular dataset continuously starting from a specified point in time.
-
C.
hasTemporalLocation
chosen
Indicates that something occurs, exists, or is valid during a specific time or time interval.
-
D.
supportsTimescale
Indicates that one entity is capable of operating with, accommodating, or being compatible with a specified timescale or range of temporal resolutions.
-
E.
hadCheckpoint
Indicates that an entity passed through, reached, or was associated with a specific checkpoint at some point in 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90584b8b881908e112c7e59163812 |
completed | March 5, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69a88727ce48819089b482cdc25453d1 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:24 p.m.