Triple
T37828605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Aberdeen |
E943133
|
entity |
| Predicate | famousBuilding |
P114274
|
FINISHED |
| Object | Marischal College |
—
|
NE NERFINISHED |
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: Marischal College | Statement: [City of Aberdeen, famousBuilding, Marischal College]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousBuilding Context triple: [City of Aberdeen, famousBuilding, Marischal College]
-
A.
emblematicBuildingLocation
Indicates that a building serves as a symbolic or representative landmark for a particular location or area.
-
B.
hasFamousStructure
chosen
Indicates that an entity possesses or is associated with a well-known or widely recognized structure.
-
C.
buildingNamed
Indicates that a particular building is known or referred to by a specified name.
-
D.
notableDome
Indicates that an entity has a dome that is significant or noteworthy in some recognized context (e.g., historically, architecturally, or culturally).
-
E.
notableBuildingAssociated
Indicates a relationship where a notable or significant building is associated with, connected to, or relevant to a given entity.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.