Triple
T16796535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stay |
E408246
|
entity |
| Predicate | hasNotableFanbase |
P48181
|
FINISHED |
| Object | Oingo Boingo fans |
—
|
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: Oingo Boingo fans | Statement: [Stay, hasNotableFanbase, Oingo Boingo fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFanbase Context triple: [Stay, hasNotableFanbase, Oingo Boingo fans]
-
A.
hasFanBaseFrom
Indicates that an entity has a significant group of supporters or followers originating from a specified place, group, or source.
-
B.
hasFanCommunity
chosen
Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
-
C.
hasStrongRegionalFanBase
Indicates that an entity enjoys particularly high popularity or support within a specific geographic region compared to other areas.
-
D.
hasFanBaseDepictedAs
Indicates that an entity has a fan base that is visually or narratively represented in some form (e.g., in media, artwork, or documentation).
-
E.
notableFan
Indicates that one entity is a well-known or especially prominent admirer or supporter of another entity.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2aa1ff48190ab9b6750bc4d7974 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.