Triple
T18927605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resolute |
E463014
|
entity |
| Predicate | hasInuktitutMeaning |
P133829
|
FINISHED |
| Object | place with no dawn |
—
|
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: place with no dawn | Statement: [Resolute, hasInuktitutMeaning, place with no dawn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInuktitutMeaning Context triple: [Resolute, hasInuktitutMeaning, place with no dawn]
-
A.
hasInuktitutName
Indicates that an entity has a name expressed in the Inuktitut language.
-
B.
hasEthnonymMeaning
Indicates that one entity is the meaning or semantic interpretation of an ethnonym (a name for an ethnic group) associated with another entity.
-
C.
hasMeaningInEstonian
Indicates that something possesses a particular meaning or interpretation in the Estonian language.
-
D.
hasMeaningInJapanese
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning when interpreted in the Japanese language.
-
E.
hasNameInAnishinaabemowin
Indicates that an entity is known by a particular name expressed in the Anishinaabemowin language.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9bdddb481908bebd32f927ed5de |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 11:59 a.m.