Triple
T19996150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Legion |
E494197
|
entity |
| Predicate | disbandedAround |
P66716
|
FINISHED |
| Object | 1820s |
—
|
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: 1820s | Statement: [British Legion, disbandedAround, 1820s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disbandedAround Context triple: [British Legion, disbandedAround, 1820s]
-
A.
disbandedDuring
chosen
Indicates that an entity ceased to exist or was formally dissolved at some point within the duration of a specified event or time period.
-
B.
disbandedAt
Indicates the time or date at which an organized group, body, or entity formally ceased to exist or operate.
-
C.
disbandmentYear
Indicates the year in which an organization, group, or entity formally ceased to exist or was dissolved.
-
D.
disbandedOrTransformed
Indicates that an entity has ceased to exist in its original form, either by being dissolved or by changing into a different organizational or structural form.
-
E.
disbandedOrAmalgamatedIn
Indicates that an entity ceased to exist in its original form on a given date, either by being formally disbanded or by being merged into 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe3fb288190a935c334e8a5d54e |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:32 p.m.