Triple
T31066412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strand |
E791682
|
entity |
| Predicate | hasMeaningInScandinavianLanguages |
P92861
|
FINISHED |
| Object | beach |
—
|
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: beach | Statement: [Strand, hasMeaningInScandinavianLanguages, beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeaningInScandinavianLanguages Context triple: [Strand, hasMeaningInScandinavianLanguages, beach]
-
A.
meaningInModernScandinavianLanguages
chosen
Indicates that something has a particular meaning or sense when used in contemporary Scandinavian languages.
-
B.
hasMeaningInOriginLanguage
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning in its original or source language.
-
C.
hasDanishNameMeaning
Indicates that an entity has a Danish name whose semantic meaning or etymology is being specified.
-
D.
hasMeaningInEstonian
Indicates that something possesses a particular meaning or interpretation in the Estonian language.
-
E.
meaningInOldNorse
Indicates that something has a particular meaning or translation in the Old Norse language.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: April 29, 2026, 9:01 p.m.