Triple
T37544538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memphis Grizzlies (WFL proposed rename) |
E933421
|
entity |
| Predicate | hasProposedHomeCity |
P42733
|
FINISHED |
| Object | Memphis |
E115438
|
NE 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: Memphis | Statement: [Memphis Grizzlies (WFL proposed rename), hasProposedHomeCity, Memphis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProposedHomeCity Context triple: [Memphis Grizzlies (WFL proposed rename), hasProposedHomeCity, Memphis]
-
A.
hasHomeCity
Indicates that an entity’s primary or official city of residence or affiliation is a specified city.
-
B.
isSettledIn
Indicates that an entity resides or has established its home or base in a particular location.
-
C.
hasPlannedCity
Indicates that an entity has a city that was deliberately designed and constructed according to a prearranged plan.
-
D.
proposedInCity
chosen
Indicates that something, such as a plan, project, or idea, was formally proposed within a particular city.
-
E.
adoptedInCity
Indicates that an adoption event took place within a specific city.
- F. None of above.
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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40afd47140819086a121f1c174489c |
completed | June 28, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.