Triple
T28804738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mantova FC |
E727340
|
entity |
| Predicate | hasDissolutionEvent |
P183659
|
FINISHED |
| Object | bankruptcy |
—
|
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: bankruptcy | Statement: [Mantova FC, hasDissolutionEvent, bankruptcy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDissolutionEvent Context triple: [Mantova FC, hasDissolutionEvent, bankruptcy]
-
A.
hasDissolutionDate
Indicates the date on which an entity, such as an organization or legal arrangement, formally ceases to exist or is officially dissolved.
-
B.
isDissolved
chosen
Indicates that an entity (such as an organization, partnership, or legal body) has formally ceased to exist or operate.
-
C.
isDissolvedBy
Indicates that one substance causes another substance to break down and go into solution.
-
D.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
-
E.
hasDissolvedOrSeparatedFrom
Indicates that one entity has formally ended, dissolved, or separated its prior association, union, or affiliation with another entity.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 28, 2026, 6:28 a.m.