Triple
T33414601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore Orioles (American League, 1901–1902) |
E855677
|
entity |
| Predicate | boroughAfterRelocation |
P176573
|
FINISHED |
| Object | Manhattan |
—
|
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: Manhattan | Statement: [Baltimore Orioles (American League, 1901–1902), boroughAfterRelocation, Manhattan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boroughAfterRelocation Context triple: [Baltimore Orioles (American League, 1901–1902), boroughAfterRelocation, Manhattan]
-
A.
cityAfterRelocation
Indicates the city where an entity is located after it has been moved or relocated from a previous place.
-
B.
countySeatMovedTo
Indicates that the official county seat was relocated from one place to another.
-
C.
locatedInOldCity
Indicates that an entity is situated within the boundaries of an old or historic part of a city.
-
D.
dateCapitalMoved
Indicates the date on which a capital city was officially relocated from one place to another.
-
E.
residenceAfterAnnexation
Indicates that an entity’s place of residence is located in a territory after that territory has been annexed by another political authority.
- F. None of above. chosen
Provenance (4 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e52a6d40819084472f6072c91e9f |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e47c13348190a10528c84a401178 |
completed | May 3, 2026, 6 a.m. |
Created at: May 1, 2026, 1:36 a.m.