Triple
T786975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Area B-5 (Catoctin Mountain Park) |
E16823
|
entity |
| Predicate | languageOfLocation |
P10892
|
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: [Area B-5 (Catoctin Mountain Park), languageOfLocation, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfLocation Context triple: [Area B-5 (Catoctin Mountain Park), languageOfLocation, English]
-
A.
regionLanguage
chosen
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
B.
standardLanguageOf
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
-
C.
majorityLanguageOf
Indicates that a given language is the primary or most widely spoken language within a specified group, region, or entity.
-
D.
languageUse
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
E.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a78171908190a38a70274bfbebf9 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50db97c8190a1c55673f4a357b4 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:38 p.m.