Triple
T8715511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weslee |
E206883
|
entity |
| Predicate | hasTypicalUsagePeriod |
P70126
|
FINISHED |
| Object | contemporary 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: contemporary era | Statement: [Weslee, hasTypicalUsagePeriod, contemporary era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalUsagePeriod Context triple: [Weslee, hasTypicalUsagePeriod, contemporary era]
-
A.
hasTypicalUseTime
chosen
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
B.
typicalUseDays
Indicates the usual or expected number of days over which something is used or intended to be used.
-
C.
hasHistoricalUsageIn
Indicates that something has been used or practiced within a particular historical period, context, or tradition.
-
D.
hasTypicalUseContext
Indicates that something is commonly or characteristically used within a particular situation, setting, or context.
-
E.
hasValidityPeriod
Indicates that something is associated with a specific time span during which it is considered valid or in effect.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cd807cc819090b58caf285b397a |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.