Triple
T1501294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota |
E33799
|
entity |
| Predicate | hasNicknamed |
P25214
|
FINISHED |
| Object | Land of 10,000 Lakes |
—
|
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: Land of 10,000 Lakes | Statement: [Minnesota, hasNicknamed, Land of 10,000 Lakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNicknamed Context triple: [Minnesota, hasNicknamed, Land of 10,000 Lakes]
-
A.
notableNickname
chosen
Indicates that one entity is a well-known or widely recognized nickname or moniker for another entity.
-
B.
isNickname
Indicates that one name is an informal or alternative name commonly used to refer to the same person or entity as another name.
-
C.
fandomNickname
Indicates that one entity is the nickname used by fans to refer to another entity (such as a person, group, or work).
-
D.
honorificNickname
Indicates that one entity is referred to by a respectful or honorific nickname by another entity or in a given context.
-
E.
academyNickname
Indicates that an entity is known by a particular informal or colloquial nickname within an academy or academic institution context.
- 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90584b8b881908e112c7e59163812 |
completed | March 5, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69a88727ce48819089b482cdc25453d1 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:24 p.m.