Triple
T445228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berkeley Landmark |
E7001
|
entity |
| Predicate | hasDesignationType |
P974
|
FINISHED |
| Object | individual landmark |
—
|
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: individual landmark | Statement: [Berkeley Landmark, hasDesignationType, individual landmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignationType Context triple: [Berkeley Landmark, hasDesignationType, individual landmark]
-
A.
hasDesignation
chosen
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
B.
hasLetterDesignation
Indicates that an entity is assigned or associated with a specific letter-based designation or code.
-
C.
designatorType
Indicates the specific role or category of a designator used to identify or reference an entity within a system or context.
-
D.
sharesDesignationTypeWith
Indicates that two entities have the same type or category of designation (e.g., title, label, or classification).
-
E.
hasAppellationType
Indicates that an entity’s name or title is associated with a specific category or type of appellation.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef479ec08190a659eead6eb0d4d0 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2eddfb5508190a4e06e1b260d8b2b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.