Triple
T8821826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Baltimore |
E209921
|
entity |
| Predicate | containsNeighborhood |
P4813
|
FINISHED |
| Object | Abell |
E754612
|
NE 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: Abell | Statement: [Central Baltimore, containsNeighborhood, Abell]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Abell Context triple: [Central Baltimore, containsNeighborhood, Abell]
-
A.
Abell
chosen
Abell is a surname most notably associated with A. S. Abell, the 19th-century American publisher who founded the Baltimore Sun newspaper.
-
B.
Abell 400
Abell 400 is a galaxy cluster notable for hosting the radio galaxy 3C 75, whose dual supermassive black holes are observed in the process of merging.
-
C.
Abell 539
Abell 539 is a rich galaxy cluster located within the Perseus–Pisces Supercluster and studied as part of large-scale structure in the universe.
-
D.
Abell 426
Abell 426, also known as the Perseus Cluster, is a massive, nearby galaxy cluster notable for its bright X-ray emission and central active galaxy NGC 1275.
-
E.
Abell 569
Abell 569 is a galaxy cluster located within the Perseus–Pisces Supercluster, one of the most prominent large-scale structures in the nearby universe.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc602ed87c8190ab772e5cbb2da68d |
completed | April 1, 2026, midnight |
| NED1 | Entity disambiguation (via context triple) | batch_69cf6fd064208190b1c8e1e1848763d2 |
completed | April 3, 2026, 7:44 a.m. |
Created at: March 30, 2026, 6:46 p.m.