Triple
T34655528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pig Beach |
E889963
|
entity |
| Predicate | languageUsedByOperators |
P91220
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Pig Beach, languageUsedByOperators, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedByOperators Context triple: [Pig Beach, languageUsedByOperators, English]
-
A.
languageOfOperator
chosen
Indicates that a particular language is used by, or associated with, a given operator in performing its functions or services.
-
B.
languageOfOperation
Indicates the language in which an entity (such as a system, service, or process) primarily operates or functions.
-
C.
languagesUsed
Indicates that one entity uses, employs, or is expressed in one or more languages associated with the other entity.
-
D.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
E.
tertiaryLanguageOfOperation
Indicates that an entity uses a specified language as its third most prominent or prioritized language of operation.
- 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00781b749c8190921c46e110cae0b0 |
completed | May 10, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_6a0077df3c8481909fabc9e84f5936e3 |
completed | May 10, 2026, 12:19 p.m. |
Created at: May 1, 2026, 2:04 a.m.