Triple
T35978874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdiocese of Bremen |
E1040500
|
entity |
| Predicate | hadMetropolitanStatus |
P24765
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Archdiocese of Bremen, hadMetropolitanStatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMetropolitanStatus Context triple: [Archdiocese of Bremen, hadMetropolitanStatus, yes]
-
A.
hasMetropolitanBoroughStatus
Indicates that an administrative area holds the legal and governmental status of a metropolitan borough.
-
B.
hasMetropolitan
Indicates that an entity is associated with, served by, or located within a specific metropolitan area.
-
C.
hasMetropolitanRankOver
Indicates that one entity has a higher metropolitan rank or status than another entity.
-
D.
metropolitanStatusHeld
chosen
Indicates that an entity holds or is assigned a particular metropolitan status (e.g., being designated as part of a metropolitan area or category).
-
E.
hasMetropolitanAuthorityOver
Indicates that one entity holds official governing or administrative authority over a metropolitan area or region associated with another 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.