Triple
T2946429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Art Modell |
E79512
|
entity |
| Predicate | teamRelocatedResult |
P44140
|
FINISHED |
| Object | creation of the Baltimore Ravens |
—
|
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: creation of the Baltimore Ravens | Statement: [Art Modell, teamRelocatedResult, creation of the Baltimore Ravens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamRelocatedResult Context triple: [Art Modell, teamRelocatedResult, creation of the Baltimore Ravens]
-
A.
teamRelocationTo
Indicates the movement of a team from one location to another as its new home or base of operations.
-
B.
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.
-
C.
formerTeamRelocation
Indicates that an entity was previously associated with a team before that team relocated to a different place.
-
D.
team2RelocatedToCurrentCity
Indicates that the second team has moved its location to the city where it is currently based.
-
E.
teamLocation
Indicates that a team is based in, associated with, or operates from a particular geographic location.
- 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98b3f86c819094526c2af611bfb5 |
completed | March 8, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:56 p.m.