Triple
T23653688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soap |
E584233
|
entity |
| Predicate | firstRunEndYear |
P91688
|
FINISHED |
| Object | 1981 |
—
|
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: 1981 | Statement: [Soap, firstRunEndYear, 1981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRunEndYear Context triple: [Soap, firstRunEndYear, 1981]
-
A.
firstRunningYear
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
-
B.
firstMajorRunYear
Indicates the year in which something (such as an event, production, or operation) first began its major or primary run.
-
C.
firstTypeEndYear
Indicates the year in which the first occurrence or instance of a particular type or category comes to an end.
-
D.
firstSeasonEndYear
chosen
Indicates the calendar year in which an entity’s first season or initial seasonal run concluded.
-
E.
firstCompleteSweepYear
Indicates the year in which an entity first achieved a complete sweep of all relevant items, events, or opponents within a defined context.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b3599128819092b6a44779889a78 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.