Triple
T26323687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Hobart Football Club |
E662186
|
entity |
| Predicate | hasTraditionalHomeStrip |
P180595
|
FINISHED |
| Object | red and blue guernsey |
—
|
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: red and blue guernsey | Statement: [North Hobart Football Club, hasTraditionalHomeStrip, red and blue guernsey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalHomeStrip Context triple: [North Hobart Football Club, hasTraditionalHomeStrip, red and blue guernsey]
-
A.
hasTraditionalHouseStyle
Indicates that an entity possesses or is characterized by a traditional style of house or residential architecture.
-
B.
hasHomeFeature
Indicates that a home possesses or includes a particular feature or amenity.
-
C.
hasCommercialStrip
Indicates that an area or entity contains or is associated with a zone characterized by a concentration of commercial businesses or retail establishments.
-
D.
hasHome
Indicates that an entity possesses or is associated with a place where it lives or is based.
-
E.
hasHouseholdFeature
Indicates that a household possesses or includes a specific feature, attribute, or amenity.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 26, 2026, 10:29 p.m.