Triple
T33328340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FFA |
E853331
|
entity |
| Predicate | hasOfficialDress |
P134513
|
FINISHED |
| Object | FFA jacket |
—
|
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: FFA jacket | Statement: [FFA, hasOfficialDress, FFA jacket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialDress Context triple: [FFA, hasOfficialDress, FFA jacket]
-
A.
hasDressCode
Indicates that a specified entity enforces or is associated with a particular set of rules governing appropriate clothing or attire.
-
B.
hasOfficialStyle
chosen
Indicates that an entity possesses a formally recognized style, manner, or form as defined by an authoritative source or standard.
-
C.
ceremonialDressFeature
Indicates that one entity is a characteristic, component, or distinguishing element of another entity’s ceremonial dress or attire.
-
D.
hasTraditionalAttire
Indicates that an entity possesses or is associated with clothing that is customary or traditional within a particular culture or community.
-
E.
hasDressNumber
Indicates that an entity (typically a player or performer) is associated with a specific dress or jersey number.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 1, 2026, 1:34 a.m.