Triple
T19732961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engstligen Falls |
E473899
|
entity |
| Predicate | tiered |
P137131
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Engstligen Falls, tiered, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tiered Context triple: [Engstligen Falls, tiered, true]
-
A.
thirdTier
Indicates that an entity occupies a third level or rank within a hierarchical structure or classification.
-
B.
hadTierSystem
Indicates that an entity implemented or used a structured tier-based system, typically organizing elements into hierarchical levels or ranks.
-
C.
traditionalTier
Indicates that an entity belongs to, or is categorized within, a conventional or historically established level, class, or rank in a tiered system.
-
D.
tierType
Indicates the classification level or rank assigned to an entity within a multi-level or hierarchical system.
-
E.
firstTier
Indicates that one entity occupies the highest or primary level, rank, or priority relative to others in a hierarchical structure.
- F. None of above. chosen
Provenance (4 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e651596b98819090bcaf05c7b74555 |
completed | April 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:47 p.m.