Triple
T28963179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Andorra |
E731966
|
entity |
| Predicate | jerseyPatternInspiredBy |
P50176
|
FINISHED |
| Object | flag of Andorra |
—
|
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: flag of Andorra | Statement: [FC Andorra, jerseyPatternInspiredBy, flag of Andorra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jerseyPatternInspiredBy Context triple: [FC Andorra, jerseyPatternInspiredBy, flag of Andorra]
-
A.
jerseyDesignInspiredBy
chosen
Indicates that the design of a jersey is based on, influenced by, or derived from another design, theme, or source.
-
B.
jerseyInspiration
Indicates that one jersey’s design, style, or elements are derived from, influenced by, or modeled after another source.
-
C.
jersey
Indicates that one entity is the jersey (sports uniform top) associated with, worn by, or representing another entity.
-
D.
jerseyDescription
Indicates that a textual description is provided for a particular jersey, such as its appearance, style, or distinguishing features.
-
E.
jerseyLogo
Indicates that a logo is displayed on or associated with a jersey as part of its design or branding.
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 8:51 a.m.