Triple
T31264679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Felsennest |
E797218
|
entity |
| Predicate | usedByRank |
P185327
|
FINISHED |
| Object | Führer |
—
|
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: Führer | Statement: [Felsennest, usedByRank, Führer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByRank Context triple: [Felsennest, usedByRank, Führer]
-
A.
usesRank
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
-
B.
usesRankingPoints
Indicates that one entity bases its ordering, evaluation, or decision-making on ranking points associated with another entity.
-
C.
rankingUsage
Indicates how an entity is used or positioned within an ordered ranking or hierarchy relative to others.
-
D.
ledByRank
Indicates that the leadership of an entity is determined or characterized by a specific rank or hierarchical position.
-
E.
usedByPosition
Indicates that something is utilized or applied by an entity occupying a particular role or position.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: April 29, 2026, 9:12 p.m.