Triple
T32906749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mitten |
E841762
|
entity |
| Predicate | hasPartCorrespondence |
P25442
|
FINISHED |
| Object | thumb corresponds to “Thumb” region of Michigan |
—
|
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: thumb corresponds to “Thumb” region of Michigan | Statement: [The Mitten, hasPartCorrespondence, thumb corresponds to “Thumb” region of Michigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartCorrespondence Context triple: [The Mitten, hasPartCorrespondence, thumb corresponds to “Thumb” region of Michigan]
-
A.
containsCorrespondenceWith
Indicates that one entity includes or holds correspondence (such as messages or communications) that is associated with or exchanged with another entity.
-
B.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
C.
partiallyCorrespondsTo
chosen
Indicates that one entity matches or aligns with another entity only in some aspects, segments, or components, rather than fully or exactly.
-
D.
hasPartIn
Indicates that an entity participates in or plays a role within a larger event, process, or composite entity.
-
E.
hasCorrespondenceForm
Indicates that there exists a specific format, template, or structural representation used for the correspondence associated with an 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
Created at: May 1, 2026, 1:19 a.m.