Triple
T25466462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Küssnachtersee |
E638186
|
entity |
| Predicate | isArmDirection |
P158573
|
FINISHED |
| Object | northern arm |
—
|
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: northern arm | Statement: [Küssnachtersee, isArmDirection, northern arm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isArmDirection Context triple: [Küssnachtersee, isArmDirection, northern arm]
-
A.
hasArm
Indicates that one entity possesses or is equipped with an arm as a physical part or component of itself.
-
B.
isForwardArmOf
Indicates that one object functions as the front or leading arm/extension of another object in a given structure or system.
-
C.
isLocalArmOf
Indicates that one entity functions as the local branch, office, or operational arm of another, typically larger or central, organization.
-
D.
isSmallerArmOf
Indicates that one arm or branch is a smaller or lesser subdivision of another arm or branch within the same overall structure.
-
E.
hasArmWidth
Indicates that one entity has a specified measurement for the width of its arm.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f74e449c8190afaa3c05496ed598 |
completed | May 2, 2026, 1:08 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:14 p.m.