Triple
T21161368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea of Sand |
E521446
|
entity |
| Predicate | literalMeaningOfLocalName |
P23078
|
FINISHED |
| Object | Sea of Sand |
—
|
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: Sea of Sand | Statement: [Sea of Sand, literalMeaningOfLocalName, Sea of Sand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literalMeaningOfLocalName Context triple: [Sea of Sand, literalMeaningOfLocalName, Sea of Sand]
-
A.
alternativeNameMeaning
Indicates that one entity expresses the meaning or interpretation of an alternative name used for another entity.
-
B.
localNameDefinition
chosen
Indicates that an entity’s locally scoped name is defined or specified within a particular context or namespace.
-
C.
languageNameMeaning
Indicates that the predicate relates a language’s name to its meaning or etymological significance.
-
D.
officialNameMeaning
Indicates the semantic meaning or etymological significance conveyed by an entity’s official name.
-
E.
literalMeaningApproximation
Indicates that one entity expresses an approximate or rough literal meaning of another entity, rather than an exact or fully precise interpretation.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72530e3388190a170c5a2a19dadfc |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:59 p.m.