Triple
T27910775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kane |
E705920
|
entity |
| Predicate | unmaskedPeriod |
P163766
|
FINISHED |
| Object | 2003-2011 |
—
|
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: 2003-2011 | Statement: [Kane, unmaskedPeriod, 2003-2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unmaskedPeriod Context triple: [Kane, unmaskedPeriod, 2003-2011]
-
A.
protectsPeriod
Indicates that one entity provides protection or safeguarding to another entity for a specified duration or time period.
-
B.
timePeriodImplied
Indicates that a time period is inferred or implied by context rather than being explicitly specified.
-
C.
nonRecognitionPeriodEnd
Indicates the point in time when a previously established period of non-recognition (e.g., of status, rights, or validity) comes to an end.
-
D.
nonRecognitionPeriodStart
Indicates the point in time when a specified non-recognition period for an entity or relationship begins.
-
E.
focusPeriodStart
Indicates the point in time at which a specified focus period or interval begins.
- F. None of above. chosen
Provenance (4 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c045bd081908e0cb2a119202e8f |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63b3039808190b00bbd19161487f3 |
completed | May 2, 2026, 5:58 p.m. |
Created at: April 27, 2026, 6:49 p.m.