Triple
T22943220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fern Grotto |
E569788
|
entity |
| Predicate | hasPrimaryLanguageForTours |
P78017
|
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: [Fern Grotto, hasPrimaryLanguageForTours, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryLanguageForTours Context triple: [Fern Grotto, hasPrimaryLanguageForTours, English]
-
A.
hasPrimaryLanguage1
Indicates that an entity’s main or most commonly used language is the specified language.
-
B.
hasPrimaryLanguageOfVisitors
Indicates that an entity is associated with the main language typically spoken or used by its visitors.
-
C.
hasPrimaryLanguageNearby
Indicates that an entity is associated with a primary language that is predominantly used or present in its immediate geographic or contextual vicinity.
-
D.
hasPrimaryTraditionalLanguage
Indicates that one entity is the main or principal traditional language associated with another entity.
-
E.
hasPrimaryLanguageOfOperations
chosen
Indicates that an entity conducts its main activities or operations primarily using a specified 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1819b65dc8190b9456346e7284ddf |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:45 p.m.