Triple
T30680267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DIDMCA |
E781032
|
entity |
| Predicate | phasesOutOverPeriod |
P162723
|
FINISHED |
| Object | six years |
—
|
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: six years | Statement: [DIDMCA, phasesOutOverPeriod, six years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phasesOutOverPeriod Context triple: [DIDMCA, phasesOutOverPeriod, six years]
-
A.
phasesOut
Indicates the process by which one entity or condition is gradually discontinued or removed in favor of another over time.
-
B.
phaseOutEndTime
Indicates the point in time when a phase-out process or period is scheduled to end.
-
C.
phaseCount
Indicates the number of distinct phases or stages associated with a given process, event, or entity.
-
D.
phaseOutBasedOn
Indicates a relationship where one entity is gradually discontinued, removed, or reduced in favor of or as a consequence of another specified factor or condition.
-
E.
graduallyPhasedOutIn
chosen
Indicates that something is discontinued or removed in a particular context or period through a slow, step-by-step process rather than all at once.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:32 p.m.