Triple
T3673223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Paul Saints |
E77926
|
entity |
| Predicate | hasNotableFanBaseTrait |
P6226
|
FINISHED |
| Object | family-friendly atmosphere |
—
|
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: family-friendly atmosphere | Statement: [St. Paul Saints, hasNotableFanBaseTrait, family-friendly atmosphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFanBaseTrait Context triple: [St. Paul Saints, hasNotableFanBaseTrait, family-friendly atmosphere]
-
A.
hasFanCommunity
Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
-
B.
hasFanBaseTension
Indicates a relationship where there is conflict, rivalry, or strained relations between the fan bases of the related entities.
-
C.
hasFan
Indicates that an entity is the admirer, supporter, or enthusiast of another entity.
-
D.
fanbaseCharacteristic
chosen
Indicates a characteristic, trait, or common quality that typically describes or distinguishes the fanbase of an entity.
-
E.
hasNotablePlayer
Indicates that an entity (such as a team or club) is associated with a player who is particularly distinguished, famous, or significant in its context.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc42f82548190b4d5f0fe7250decb |
completed | March 8, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.