Triple
T1277217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Africa/Blantyre |
E27241
|
entity |
| Predicate | usedForTimestamps |
P20333
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Africa/Blantyre, usedForTimestamps, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForTimestamps Context triple: [Africa/Blantyre, usedForTimestamps, true]
-
A.
supportsTimestamps
chosen
Indicates that the subject is capable of handling, storing, or recognizing timestamp information associated with relevant data or events.
-
B.
usedForCivilTimeIn
Indicates that something (typically a time scale or standard) is used as the basis for keeping official civil time within a specified region or jurisdiction.
-
C.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
D.
usedUntil
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
E.
inUseSince
Indicates that an entity has been actively in use starting from a specified 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.