Triple
T32885373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Kilda Football Club |
E841183
|
entity |
| Predicate | hasSupporterBaseCharacteristic |
P98916
|
FINISHED |
| Object | passionate |
—
|
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: passionate | Statement: [St Kilda Football Club, hasSupporterBaseCharacteristic, passionate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupporterBaseCharacteristic Context triple: [St Kilda Football Club, hasSupporterBaseCharacteristic, passionate]
-
A.
hasSupporter
Indicates that one entity supports, endorses, or backs another entity.
-
B.
notableSupportBaseCharacteristic
chosen
Indicates that a subject’s base of support is distinguished by a particular notable characteristic or quality.
-
C.
hasSupporterBaseLocation
Indicates that an entity’s base of supporters is located in a specified place or region.
-
D.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in another entity.
-
E.
hasSupporterDetail
Indicates that an entity is associated with specific information or attributes about a supporter related to it.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: May 1, 2026, 1:18 a.m.