Triple
T31120122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota congressional delegation |
E793198
|
entity |
| Predicate | hasCollectiveInformalName |
P52939
|
FINISHED |
| Object | Minnesota delegation |
E793198
|
NE 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: Minnesota delegation | Statement: [Minnesota congressional delegation, hasCollectiveInformalName, Minnesota delegation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectiveInformalName Context triple: [Minnesota congressional delegation, hasCollectiveInformalName, Minnesota delegation]
-
A.
usedCollectiveName
Indicates that a group of entities is referred to by a shared collective name.
-
B.
collectivelyKnownAs
chosen
Indicates that multiple entities are referred to together under a single shared name or designation.
-
C.
hasCommunalAppellation
Indicates that an entity shares a common or collective name or designation with a group or community.
-
D.
hasPoliticalColloquialName
Indicates that an entity is known by an informal or popularly used political nickname or colloquial title.
-
E.
collectiveNameForm
Indicates that one entity serves as the collective or group name form used to refer to multiple members of another entity or class.
- F. None of above.
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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01c74a72fc819084826c6c292af03a |
completed | May 11, 2026, 12:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2938bf1b008190bc564faa0d2ffa00 |
completed | June 10, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_6a01c624103c819087cb35a71c5868b6 |
completed | May 11, 2026, 12:05 p.m. |
Created at: April 29, 2026, 9:04 p.m.