Triple
T22200441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lions |
E548665
|
entity |
| Predicate | associatedWithNicknameType |
P64821
|
FINISHED |
| Object | club nickname |
—
|
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: club nickname | Statement: [The Lions, associatedWithNicknameType, club nickname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithNicknameType Context triple: [The Lions, associatedWithNicknameType, club nickname]
-
A.
associatedWithCityNicknameType
chosen
Indicates a relationship where a city is linked to a specific type or category of nickname it is known by.
-
B.
associatedWithArtistNickname
Indicates that an entity is connected to or identified by a particular artist’s nickname or pseudonym.
-
C.
hasNicknamedEntityType
Indicates that an entity is associated with another entity type specifically in the role of being its nickname or informal name.
-
D.
usesNicknameOf
Indicates that one entity refers to another entity by a nickname derived from or associated with that other entity’s name.
-
E.
hasNicknameStatus
Indicates that an entity holds a particular status or classification specifically related to its nickname.
- F. None of above.
Provenance (3 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aea51d48190a570cd36c106ab78 |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.