Triple
T15323207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Luke's F.C. |
E366344
|
entity |
| Predicate | dissolvedAsDistinctEntity |
P90528
|
FINISHED |
| Object | 1880s |
—
|
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: 1880s | Statement: [St. Luke's F.C., dissolvedAsDistinctEntity, 1880s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolvedAsDistinctEntity Context triple: [St. Luke's F.C., dissolvedAsDistinctEntity, 1880s]
-
A.
dissolvedAsDistinctGroup
chosen
Indicates that a previously separate group ceased to exist as an independent, distinct entity (e.g., through disbanding, merging, or absorption).
-
B.
dissolvedAs
Indicates that one entity ceased to exist or operate in its original form and was formally absorbed, merged, or reconstituted as another entity.
-
C.
dissolved
Indicates that one substance has been mixed into another so thoroughly that it forms a uniform solution and is no longer distinguishable as a separate phase.
-
D.
dissolvedInPart
Indicates that one substance is only partially dissolved in another, resulting in an incomplete or limited dissolution.
-
E.
dissolvedDueTo
Indicates that a relationship, agreement, or entity came to an end as a result of a specified cause or event.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd5ce0c819093c9a14de549dff6 |
completed | April 16, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.