Triple
T31896000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke City Derby |
E814283
|
entity |
| Predicate | cityNicknameOrigin |
P172706
|
FINISHED |
| Object | named after Albuquerque's nickname "Duke City" |
—
|
NE NERFINISHED |
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: named after Albuquerque's nickname "Duke City" | Statement: [Duke City Derby, cityNicknameOrigin, named after Albuquerque's nickname "Duke City"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityNicknameOrigin Context triple: [Duke City Derby, cityNicknameOrigin, named after Albuquerque's nickname "Duke City"]
-
A.
cityNickname
Indicates that one entity is commonly used as an informal or alternative name for a city.
-
B.
cityNicknameAssociation
Indicates an associative relationship where a particular nickname is used to refer to or characterize a specific city.
-
C.
cityNickNameForFanBase
Indicates that a particular nickname is used by fans to refer to a city or its fan base.
-
D.
isInCityNicknamed
Indicates that one entity is located in a city that is known by a particular nickname.
-
E.
homeCityLandmarkReferencedInNickname
Indicates that a landmark from a person's home city is mentioned or alluded to in their nickname.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b1647918819085ec718e13f9926a |
completed | May 3, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 30, 2026, 11:58 p.m.