Triple
T11362470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami Confederacy |
E269117
|
entity |
| Predicate | dissipatedBy |
P98922
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Miami Confederacy, dissipatedBy, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissipatedBy Context triple: [Miami Confederacy, dissipatedBy, early 19th century]
-
A.
dissipatedIn
Indicates that something (such as energy, heat, or a substance) is lost, spread out, or converted within a particular medium, location, or system.
-
B.
dissipatedOn
Indicates that something (such as energy, force, or a substance) is dispersed, lost, or converted into a less usable form on or within a particular medium, surface, or system.
-
C.
dismantledBy
Indicates that something has been taken apart, disassembled, or broken down by a particular agent or entity.
-
D.
dissolvedDueTo
Indicates that a relationship, agreement, or entity came to an end as a result of a specified cause or event.
-
E.
dissolvedInPart
Indicates that one substance is only partially dissolved in another, resulting in an incomplete or limited dissolution.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e7022d508190996f9be0847c2b41 |
completed | April 9, 2026, 5:50 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:33 p.m.