Triple
T33600715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalgumbun |
E860708
|
entity |
| Predicate | hasEuropeanName |
P161028
|
FINISHED |
| Object | Mount Lindesay |
—
|
NE NERFINISHED |
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: Mount Lindesay | Statement: [Jalgumbun, hasEuropeanName, Mount Lindesay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEuropeanName Context triple: [Jalgumbun, hasEuropeanName, Mount Lindesay]
-
A.
hasEnglishName
Indicates that an entity is associated with a name expressed in the English language.
-
B.
EuropeanNameVariant
chosen
Indicates that one name is a variant or alternative form of another name as used in a European language or cultural context.
-
C.
hasFranconianName
Indicates that an entity is associated with a name or designation in the Franconian language or dialect.
-
D.
hasEasternName
Indicates that an entity is associated with or known by a name used in an Eastern language or cultural context.
-
E.
hasLatinName
Indicates that an entity is associated with a specific Latin (scientific) name.
- 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f7aa07a48190b831b21bfb061db1 |
completed | May 3, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:41 a.m.