Triple
T11280315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Flying Squirrels |
E267046
|
entity |
| Predicate | relocatedToRichmond |
P98899
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Richmond Flying Squirrels, relocatedToRichmond, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocatedToRichmond Context triple: [Richmond Flying Squirrels, relocatedToRichmond, 2010]
-
A.
relocatedToWashingtonYear
Indicates the year in which an entity moved or was transferred to Washington as its new location.
-
B.
locationRelativeToRichmond
Indicates the spatial or geographic position of one place in relation to the reference location Richmond.
-
C.
relocationYearToArlington
Indicates the year in which an entity moved or was relocated to Arlington.
-
D.
countySeatMovedTo
Indicates that the official county seat was relocated from one place to another.
-
E.
returnToVirginia
Indicates that an entity goes back or moves again to the location identified as Virginia after having been away.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e969b3448190940e2bd499d2d7de |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796cf74308190a5b29d0dd82954a2 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:31 p.m.