Triple
T19128263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mistake by the Lake |
E468242
|
entity |
| Predicate | appliedToStatus |
P134515
|
FINISHED |
| Object | long-demolished stadium |
—
|
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: long-demolished stadium | Statement: [The Mistake by the Lake, appliedToStatus, long-demolished stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToStatus Context triple: [The Mistake by the Lake, appliedToStatus, long-demolished stadium]
-
A.
fullyAppliedTo
Indicates that an action, function, or process has been completely and exhaustively applied to a target entity, with no remaining parameters or partial application.
-
B.
appliedWhen
Indicates the condition, time, or circumstances under which something (such as a rule, action, or effect) becomes applicable or is carried out.
-
C.
appliedFrom
Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
-
D.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
-
E.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ceb5808190b3b53d9e8df3605a |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.