Triple
T3218460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore Ravens vs Cleveland Browns |
E67452
|
entity |
| Predicate | originalBrownsRelocationYear |
P46578
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Baltimore Ravens vs Cleveland Browns, originalBrownsRelocationYear, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBrownsRelocationYear Context triple: [Baltimore Ravens vs Cleveland Browns, originalBrownsRelocationYear, 1996]
-
A.
team2RelocatedToCurrentCity
Indicates that the second team has moved its location to the city where it is currently based.
-
B.
formerTeamRelocation
Indicates that an entity was previously associated with a team before that team relocated to a different place.
-
C.
teamRelocatedFrom
Indicates that a team previously based in one location has moved its home base or operations from that original location to a different one.
-
D.
teamRelocationTo
Indicates the movement of a team from one location to another as its new home or base of operations.
-
E.
teamRelocatedResult
Indicates that a sports team has changed its home location and specifies the outcome or status resulting from that relocation.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab0c48b481909d1bd9dc41dfa8c2 |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada148e9108190b363dd0f1a94ac8e |
completed | March 8, 2026, 4:18 p.m. |
Created at: March 8, 2026, 3:08 p.m.