Triple
T33414593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore Orioles (American League, 1901–1902) |
E855677
|
entity |
| Predicate | homeCityRelocation |
P100317
|
FINISHED |
| Object | moved from Baltimore to New York in 1903 |
—
|
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: moved from Baltimore to New York in 1903 | Statement: [Baltimore Orioles (American League, 1901–1902), homeCityRelocation, moved from Baltimore to New York in 1903]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCityRelocation Context triple: [Baltimore Orioles (American League, 1901–1902), homeCityRelocation, moved from Baltimore to New York in 1903]
-
A.
cityAfterRelocation
chosen
Indicates the city where an entity is located after it has been moved or relocated from a previous place.
-
B.
relocatedWithinCity
Indicates that an entity moved from one location to another within the same city.
-
C.
homeCityOf
Indicates that a particular city is the primary place of residence or origin for a given person or organization.
-
D.
homeCityRole
Indicates that an entity holds or held a specific role, position, or function associated with their home city.
-
E.
homeCitySince
Indicates the city that has served as an entity’s home starting from a specified point in time.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:36 a.m.