Triple
T29655851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team Liquid |
E750260
|
entity |
| Predicate | hasLogoDescription |
P5819
|
FINISHED |
| Object | stylized horse head in a shield |
—
|
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: stylized horse head in a shield | Statement: [Team Liquid, hasLogoDescription, stylized horse head in a shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLogoDescription Context triple: [Team Liquid, hasLogoDescription, stylized horse head in a shield]
-
A.
hasLogoText
Indicates that an entity’s logo includes specific textual content or wording.
-
B.
hasLogoStyle
Indicates that an entity’s logo possesses or is characterized by a particular visual style or design approach.
-
C.
logoDescription
chosen
Indicates a textual description that explains the appearance, style, or content of a logo.
-
D.
hasLogoShape
Indicates that an entity’s logo is characterized by or takes the form of a specified geometric or visual shape.
-
E.
logoName
Indicates the textual name or label associated with a logo.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 28, 2026, 6:55 p.m.