Triple
T13767686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brackenberg |
E330792
|
entity |
| Predicate | associatedWithFeatureType |
P101663
|
FINISHED |
| Object | mountain peak |
—
|
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: mountain peak | Statement: [Brackenberg, associatedWithFeatureType, mountain peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFeatureType Context triple: [Brackenberg, associatedWithFeatureType, mountain peak]
-
A.
associatedWithFlag
Indicates a relationship where an entity is linked or connected to a particular flag, such as a national, organizational, or symbolic banner.
-
B.
includesFeatureTypes
chosen
Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
-
C.
associatedWithAuthorType
Indicates that one entity has a specified type of association or role in relation to an author.
-
D.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
E.
associatedWithMode
Indicates a relationship in which something is linked or connected to a particular mode, method, or manner of operation or behavior.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0227f2c48190983ccc9395e4e7a2 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:10 p.m.