Triple
T10124828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M40 |
E226183
|
entity |
| Predicate | extendedInPeriod |
P10550
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [M40, extendedInPeriod, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendedInPeriod Context triple: [M40, extendedInPeriod, 1980s]
-
A.
extendedIn
Indicates that one entity continues, prolongs, or expands the scope, duration, or range of another entity.
-
B.
continuedIntoPeriod
chosen
Indicates that an action, state, or relationship that began earlier persisted without interruption into a specified later time period.
-
C.
extendedFor
Indicates that something has been lengthened in duration, scope, or extent specifically for the benefit or use of another entity.
-
D.
extensionOpeningPeriod
Indicates the time span during which an extension (such as a facility, service, or feature) is open or available for use.
-
E.
extendedIndefinitelyOn
Indicates that something was prolonged or continued without a specified end point in relation to something else.
- 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2ebe4548190a484c145639d92f0 |
completed | April 2, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:05 p.m.