Triple
T37819697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Capitan base approach trails |
E942874
|
entity |
| Predicate | languageOfTopos |
P24399
|
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: [El Capitan base approach trails, languageOfTopos, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfTopos Context triple: [El Capitan base approach trails, languageOfTopos, English]
-
A.
languageOfTopLevelAdministration
Indicates the language officially used by the highest level of an administrative or governmental authority to conduct its functions and affairs.
-
B.
languageOfTheme
Indicates that a particular language is used to express, describe, or label a given theme or subject.
-
C.
languagePreservedBy
Indicates that a language continues to exist, be maintained, or be kept from extinction through the efforts, practices, or protection of a specified agent or entity.
-
D.
languageCategory
Indicates the classification relationship where a language is assigned to a particular linguistic or functional category.
-
E.
hasLanguageOfToponym
chosen
Indicates that a place name (toponym) is expressed in or associated with a particular 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a01b935e3948190a7af37b07938d618 |
completed | May 11, 2026, 11:10 a.m. |
| PD | Predicate disambiguation | batch_6a01b8d198b48190b01e16ac9ce7e7bd |
completed | May 11, 2026, 11:09 a.m. |
Created at: May 3, 2026, 4:19 p.m.